IdP Configuration - Okta
On this page
SingleStore SCIM supports Okta with the SCIM 2.
Prerequisites
-
RBAC authorization for the Organization Team feature.
-
RBAC user sync for the Engine RBAC at SingleStore database level.
Configure SCIM Provisioning
-
On the Okta Portal, select General tab.
-
Navigate to App Settings and select Edit.
-
Select Provisioning > SCIM > Save.
-
In the Provisioning tab, select Settings > Integration > Edit.
-
Enter the endpoint URL from SingleStore SCIM configuration in SCIM connector base URL.
-
Enter userName in Unique identifier field for users.
-
Select the following in Supported provisioning actions:
-
Push New Users
-
Push Profile Updates
-
Push Groups
-
-
Select HTTP Header in Authentication Mode.
-
Enter the secret token from SingleStore SCIM configuration in Authorization.
-
Select Test Connector Configuration.
Okta displays the test results. -
Navigate to Provisioning > To App.
-
Select Edit to enable the following:
-
Create Users
-
Update User Attributes
-
Deactivate Users
-
Remarks
-
Okta separates provisioning into two categories:
-
Assignments for user information.
-
Push Groups for group information.
To sync groups and memberships, add the group in Push Groups and assign it in Assignments
-
-
When changing the SCIM endpoint in the same Okta app integration, SingleStore does not recommend deleting groups in the target application before removing them from Push Groups.
Otherwise, Okta throws an error for updates to the SCIM endpoint instead of creating groups in the new (empty) SCIM endpoint. . -
If the SCIM endpoint is changed, reset or refresh the SCIM configuration in Okta.
-
The primary email is the unique identifier in SingleStore organization, changing it triggers an update to the user matched to the new primary email in Okta.
Last modified: November 27, 2024