Overview
This guide provides step-by-step instructions to integrate Kion with Okta using SCIM 2.0. SCIM (System for Cross-domain Identity Management) enables Okta to automate the creation, updating, and deactivation of users and groups in Kion.
Supported Features
| Feature | Supported |
|---|---|
| Create Users | ✅ |
| Update User Attributes | ✅ |
| Deactivate Users | ✅ |
| Push Groups | ✅ |
| Update Group Memberships | ✅ |
| Import Users | ❌ |
| Import Groups | ❌ |
Note: Provisioning is one-way from Okta → Kion. Importing users or groups from Kion to Okta is not supported.
Prerequisites
- Your Kion instance URL (e.g., https://<yourcompany.kion.io>)
- A Kion IDMS administrator account
- An Okta administrator account
- Okta should already be configured in Kion as a SAML IDMS. Follow the steps in this article to create this configuration before proceeding.
- Network Communication from Okta to your Kion instance. For more information on Okta's Public IP Addresses, reference their support article. Okta then maps the corresponding IP ranges for their cells in this article. You may need to edit the Security Group on your Kion User Load Balancer to allow this traffic.
Configuration Steps
Step 1: Enable SCIM and Generate Token in Kion
- Log in to Kion as an administrator.
- Navigate to Users > Identity Management Systems.
- Click on the existing Okta IDMS and browse to the SCIM Key tab.
- Click Generate Token.
- Copy the token — you'll use it in Okta later under the Provisioning tab.
Step 2: Configure the Okta SCIM Integration
A. Add the SCIM Base URL (General Tab)
- In the Okta Admin Console, go to: Applications > Applications > [Your Kion App]
- Click on the General tab.
- Under App Settings, click Edit.
- In the SCIM connector base URL field, enter:
https://<yourcompany.kion.io>/api/scim - Click Save.
B. Enable API Integration (Provisioning Tab)
- Go to the Provisioning tab.
- Click Configure API Integration.
- Check Enable API Integration.
- In the Authorization field, enter your token as provided from the Kion application.
- Click Test API Credentials.
- Once successful, click Save.
Step 3: Enable SCIM Provisioning Features
Under Provisioning > To App, enable the following:
- Create Users ✅
- Update User Attributes ✅
- Deactivate Users ✅
Click Save after enabling each option.
Step 4: Provision Users
If you are transitioning an existing IDMS with users already present in Kion, you must also provision users with Okta so that existing user objects are associated properly. Otherwise, synchronization of those objects will fail. Follow these steps:
- Go to the Assignments.
- Select Provision User. You will be prompted to create a job to provision existing users. Select OK.
- This job will run in the background. Monitor the status of this job using the View Logs link at the top of the Application page.
- You should see a message that shows "Provision sync job started" to indicate that the process has started. If you see a message that just shows "FAILURE", click on that message to reveal the cause.
- You will know this process has finished when you see "Provision sync job completed SUCCESS" in the logs.
Supported User Attributes
| Okta Attribute | Kion Field |
|---|---|
| userName | username (Required) |
| givenName | First Name |
| familyName | Last Name |
| active | Active/Inactive |
Note: userName (username) must be unique in Kion and is used as the primary identifier.
Group Provisioning Behavior
- Groups pushed from Okta are created in Kion.
- Group membership updates are synced in Kion.
- Group roles and permissions must be manually configured in Kion.
Limitations
- ❌ Users and groups cannot be imported from Kion to Okta.
- ✅ SCIM provisioning is one-way (Okta → Kion).
Troubleshooting
| Issue | Resolution |
|---|---|
| 401 Unauthorized error | Verify the token is correctly formatted. The token field should contain only the token value. Do not prefix with any values such as "Bearer ". |
| SCIM test fails in Okta |
|
| Attributes not syncing | Check field mappings and supported attributes. |
| Service Temporarily Unavailable | The remote Kion instance may be stopped and should be started. |
| Connect to <hostname> [<hostname>/<IP>] failed: Connect timed out |
|
| 504 error while testing connectivity to Kion from Okta |
|