You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/glc-scim-api-integration-with-okta-scim-adapter-1.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,11 +21,11 @@ The Okta SCIM adapter application can be installed from the Okta Integration Net
21
21
22
22
# Configuring a SCIM application in Okta.
23
23
24
-
* Step 1: In the Okta Admin Console, deploy an application from the app catalog:\
25
-
a. Go to **Applications** > **Browse App Catalog**.\
26
-
b. In the search bar type SCIM 2.0, and find the app called: SCIM 2.0 Test App (OAuth Bearer Token).\
24
+
* Step 1: In the Okta Admin Console, deploy an application from the app catalog:
25
+
a. Go to **Applications** > **Browse App Catalog**.
26
+
b. In the search bar type SCIM 2.0, and find the app called: SCIM 2.0 Test App (OAuth Bearer Token).
27
27
c. Select the application and then click **Add Integration**.
28
-
* Step 2: In the Add Scim2.0 Test App page, do the following:\
28
+
* Step 2: In the Add Scim2.0 Test App page, do the following:
29
29
a. Change the application label name if you want and make sure **Automatically log in when user lands on login page** is checked.
30
30
31
31

@@ -34,12 +34,12 @@ The Okta SCIM adapter application can be installed from the Okta Integration Net
34
34
35
35
b. Click **Next**. On the following page, click **Done**.
36
36
37
-
Step 3: After the application is created, configure the integration:\
38
-
a. Click the **Provisioning** tab, then select **Configure API Integration**.\
39
-
b. Select the **Enable API Integration** check box.\
40
-
c. In the SCIM 2.0 Base Url field, enter: https://sps.us1.greenlake-hpe.com/v1alpha1/scimproxy.\
41
-
d. In the OAuth Bearer Token field:\[link to create long-lived tokens for user provisioning] Step 2 & 3\
42
-
e. Uncheck the box for the Import Groups option.\
37
+
Step 3: After the application is created, configure the integration:
38
+
a. Click the **Provisioning** tab, then select **Configure API Integration**.
39
+
b. Select the **Enable API Integration** check box.
40
+
c. In the SCIM 2.0 Base Url field, enter: https://sps.us1.greenlake-hpe.com/v1alpha1/scimproxy.
41
+
d. In the OAuth Bearer Token field:[link to create long-lived tokens for user provisioning] Step 2 & 3
42
+
e. Uncheck the box for the Import Groups option.
43
43
f. Test that the URL and token are valid by clicking **Test API Credentials**, then click **Save**. If everything is correct, the following message is shown:
44
44
45
45
* SCIM 2.0 Base Url: https://sps.us1.greenlake-hpe.com/v1alpha1/scimproxy
@@ -51,7 +51,7 @@ After URL and Token are added test to make sure they are valid by clicking > **T
51
51
52
52

53
53
54
-
* Step 4. Configure the synchronization settings:\
54
+
* Step 4. Configure the synchronization settings:
55
55
a. Under the **Provisioning** tab > **To App** section, enable these settings:
0 commit comments