| Table of Contents | ||
|---|---|---|
|
...
Enter a descriptive name for the SCIM directory and tenant configuration. Appears in the application directory list as "SCIM: <name>".
Make a note of the Application secret is used to configure the identity provider laterfor later use in Configuring Okta. Use the suggested value or create your own.
Click Next.
...
Step 3 Configure SCIM in Okta
...
Login to the Okta admin portal
In the left menu, click Applications and then click submenu Applications.
Add integration
On the application page, click Browse App Catalog and search for Kantega.
Select Kantega SSO,then click Add integration button
Enter an appropriate Application label in General Settings and click Next.
Click Done in Sign-on Options. In this case …. kan bruke samme app i SAML eller OIDC
Enable provisioning
Go to the Provisioning tab and Click Configure API Integration.
Enable API integration
Check Enable API integration
Buildthe correct SCIM 2.0 Base Url to insert in API Integration page (see below). Use parts of the URL you see in Kantega SSO setup. This might look like for example:
https://confluence-test.example.com/plugins/servlet/ksso/scim/ra8njxzor7o2/v2while when this URL is exposed on the internet through your firewall it may look for example like this:https://scimtest.example.com/confluence-test/scim/ra8njxzor7o2/v2.
See more about network setup for SCIM here.Paste the Application secret you copied erlier in Kantega SSO SCIM wizard into Oauth Bearer Token
Uncheck Import Groups
Click the button Test API integration. If the entered API credentials are correct a success message is displayed, then click Save.
Configure To App settings
In the To App settings, enable Create Users, Update User Attributes, and Deactivate Users. Leave Sync Password unselected. You should not need to change the user mapping settings on this screen.
Configure Assignments
Now set up what groups/users should be synchronized.
Press the Assignments tab. Then press Assign and either add people or groups. You may then select the group Everyone to get all people in Okta synced over SCIM to your Atlassian product. Follow the Assign steps and press Save and Go Back, click the Done button in the end.
Configure Push Groups
At this point, any user or group assigned to the SCIM application in Okta will be provisioned to the Atlassian app (Jira, Confluence or Bitbucket). However, you still need to explicitly specify the groups to provision.
To do this, navigate to the Push Groupstab and click the Push Groups button. Either add groups by name or create a rule.
SCIM should now be configured and working and both assigned users and also the specified groups should be pushed by SCIM to Kantega SSO.
...