About SCIM provisioning for Okta
Introduction to Okta Automated Provisioning with SCIM
With Okta as your identity provider, you can enable efficient provisioning and management of your organization’s user accounts in Eptura. The Eptura SCIM integration allows Okta to serve as a single identity manager for adding and removing users, and for provisioning user groups.
Our SCIM integration supports SCIM version 2.0.
About this guide
The SCIM provisioning for Okta guide is written for administrators and assumes familiarity with Okta; basic identity management concepts; and the SCIM standard.
The key steps are provided, however, this is not a comprehensive guide. For utilizing the full potential of SCIM, please refer to the SCIM 2.0 protocol specification http://www.simplecloud.info/#Specification.
Prerequisites
The following is required to set up the Eptura SCIM application in Okta.
- Admin permissions to your Okta organization’s account.
- Eptura SCIM API URL
- Long-lived SCIM token generated from SCIM Token Provider (up to 10 years).
Learn more: How to generate a SCIM token
Supported actions
When the SCIM integration between Okta and Eptura is ready, the following actions performed from Okta are applied to the corresponding Eptura user accounts.
Action in Okta |
Notes |
|---|---|
|
Create users |
Eptura requires a unique username for each user. Our SCIM API rejects the SCIM User creation if a username already exists in Eptura. |
|
Delete users |
Users are marked as inactive in Eptura when deleted from Okta. |
|
Update user attributes |
The Eptura user account is automatically updated when user attributes are updated in Okta. |
|
Deactivate Users |
The Eptura user account is deactivated when the Okta account is deactivated or the user’s access to Eptura is disabled through Okta. |
|
Push Group |
Push group from Okta creates a corresponding group in Eptura. Group members who already exist in Eptura are mapped to the Eptura group if 'Push group memberships immediately' is enabled. |