![]() ![]() Select the Namely field from the dropdown in the Directory Field column for each required field. On the Directory Attributes tab, map the Namely fields that you want to import to OneLogin. If authentication fails, a red banner will let you know. After a successful authentication, you'll see a green banner accross the top of the page that declares success. Wait a few seconds for the authentication to finish. The API token is the permanent access token that you generated for Namely API access in step 1. The Subdomain is the yourcompany part of To prevent OneLogin and third-party directories (like Active Directory) from replacing a terminated user's work email with their personal email, you can use the Do not create disabled users and Do not update disabled users options.Įnter the API settings required to connect to Namely. Namely's offboarding protocol populates the employee's work email address field with their personal email address. This prevents OneLogin from changing the user's email address when Namely performs its offboarding protocol (see note, below). If you want to prevent Namely's offboarding protocol from changing the user's email address (see note below) in OneLogin, you must also select Do not update disabled users.ĭo not create disabled users: select to prevent disabled Namely users from being imported to OneLogin when you initially set up the integration.ĭo not update disabled users: select to switch the OneLogin user status to disabled when users are disabled in Namely, while preventing any other attributes from being updated in the OneLogin user record. If you select this option alone, the disabled OneLogin user will continue to be updated whenever the disabled Namely user is updated. Sync user status: select to update a user's status in OneLogin when they're disabled in Namely. Your can select any or all of the following options: (Optional) Set your import and synchronization settings for users who are disabled in Namely. To use this directory connector to import users from Namely to OneLogin, select Enabled under Importing Users (enabled by default). See the OneLogin documentation for your directory integration for more information.Ĭlick Save to enable additional configuration fields and tabs. If you choose another integrated directory, you must also configure OneLogin to export new users to that directory. You can choose to have OneLogin manage user authentication (in which case you manage and store encrypted passwords in OneLogin), or you can choose any third-party directory (like Active Directory, for example) that you have already integrated with OneLogin to store passwords and manage authentication. Give the directory a name, and then select which directory you want to Authenticate users in. Log into OneLogin as an administrator and go to Users > Directories. The Namely administrator account that you use to generate the permanent access token should have permission to view only the users (and user attributes) that you want to import to OneLogin. To learn more about how to generate a permanent access token, see Namely's API authentication documentation. Log into Namely as an administrator and get a permanent access token for the Namely API. To set up OneLogin's Namely directory connector: To avoid this behavior in OneLogin, use the "Do not create disabled users" and "Do not update disabled users" options when you set up the integration. This means that an employee's personal email address will be passed to the OneLogin directory. ![]() Namely populates a user's work email address field with their personal email address after they are terminated. This topic describes how to import users from Namely to OneLogin using the Namely directory connector, essentially treating Namely as your user directory of record. ![]()
0 Comments
Leave a Reply. |