- 2 Minutes to read
User Provisioning setup with Okta
- 2 Minutes to read
Connect your SCIM API service to Okta
This guide teaches you how to create and configure SCIM integrations.
Note: Please make sure you have enough NordLayer member licenses for all Azure AD users before proceeding with the Provisioning setup.
Sign up for an Okta Developer account;
Click the link in the signup email to open your Admin Console;
Select Applications > Applications;
Click Browse App Catalog;
Search for SCIM 2.0 Test App (OAuth Bearer Token);
Click Add Integration;
On the General Settings page: Set the name of your application, choose if it’s hidden from general and mobile users, and choose if users are automatically signed in from the landing page. Click Next;
Choose the sign-in method for your integration on the Sign-On Options page;
Click Done to create the integration;
Click the Provisioning tab, then in the main panel click Configure API Integration. Select the Enable API Integration checkbox;
Go to the NordLayer Control Panel;
- Turn the toggle switch on and copy the Tenant URL and Secret Token values;
- Paste the Tenant URL and Secret Token values in Okta for your SCIM server. Click Continue in the NordLayer Control Panel;
- Test the credentials by clicking Test API Credentials, which attempts to connect to Okta. If there’s an error, check the credentials entered above.
Click Save to complete the API integration;
- On the Assignments tab, ensure that the right users and groups in your organization are assigned to the app integration.
Click Edit to make changes as represented in the screenshot below:
More information about Okta provisioning can be found here.
User Provisioning with Okta in NordLayer Control Panel
This is how it looks when User Provisioning with Okta is enabled. Notice the important message reminding you to enable Okta as a login method.
Note: Be aware that you’ll lose the integration between SCIM and your NordLayer Control Panel if the feature is disabled or if you add new credentials to Okta settings.
Once you’ve enabled the feature and provisioned at least one member or team, you’ll receive a message indicating that you can only edit provisioned members or teams in their source (Okta in this case). It means provisioned members and teams become read-only; you won’t be able to edit or delete them in the NordLayer Control Panel.
Also, provisioned members and teams will have the Okta icons on their avatar to separate them from manually created members and teams.
You can still invite members and create teams manually when this feature is enabled. It means there’s the possibility to have provisioned and manually created members and teams in your organization.
- Manually created members cannot be added to provisioned teams. It means when you’re inviting new members (via the “Invite new member” button in the member list), teams listed under “Assign to team (optional)” are automatically filtered to only display manually created teams.
- Provisioned members can be added to manually created teams (“Create team” in teams list or “Add a member” in inner team page).
If this feature is disabled and you have provisioned members, these members will become editable. The Okta icon will still be seen on the member’s or team’s avatars to separate them.
Note: If you edited provisioned info, i.e., a team’s name, and you turn on Provisioning again, be aware Okta won’t be able to find the team and will create a new one. The same condition will apply to members if they change their email addresses.
See logged actions like turning on or off the feature and any other actions triggered by SCIM Provisioning under Activity > Actions:
Note: In case you have any questions or are experiencing any issues, please feel free to contact our 24/7 customer support team.