@@ -26,9 +26,7 @@ Important Notes
2626--------------- 
2727
2828-  This article explains how to set up SSO using SCIM/ULM configuration.
29-    If you need to set up SSO using **SAML configuration ** instead,
30-    please see `this 
31-    article <https://help.victorops.com/knowledge-base/single-sign-sso/> `__.
29+    If you need to set up SSO using **SAML configuration ** instead, see :ref: `single-sign-sso `
3230-  Configuring SCIM Single Sign-On and initial activation of Okta
3331   provisioning with Splunk On-Call (formerly VictorOps) is currently
3432   not a self-service process and requires contacting the Support team.
@@ -152,10 +150,8 @@ your clipboard, and click **Done**.
152150
153151
154152
155- 8. Once you configure the **General ** and **Sign-On ** options, please
156- `open a support 
157- ticket <https://help.victorops.com/knowledge-base/important-splunk-on-call-support-changes-coming-nov-11th/> `__
158- with subject “Okta SCIM setup request” and ask to configure Okta SCIM
153+ 8. Once you configure the **General ** and **Sign-On ** options, please open a support
154+ ticket with subject “Okta SCIM setup request” and ask to configure Okta SCIM
159155SSO for your Splunk On-Call organization. Provide the URL link you
160156copied from the **Identity Provider metadata** from step 7 above and the
161157list of users you will be assigning to the VictorOps (Beta) App in Okta.
@@ -176,12 +172,12 @@ login as Global Admin to Splunk On-Call.
176172
1771732. Navigate to **Integrations** >> **API **. If API Access is disabled,
178174click on **Activate API Access**. More details on API access can be
179- found ` here <https://help.victorops.com/knowledge-base/ api/>`__ .
175+ found  here :ref: ` spoc- api` .
180176
181- 3 . Click on **Integrations >> 3rd Party Integrations **. Search for
177+ 1 . Click on **Integrations >> 3rd Party Integrations **. Search for
182178   “Okta” in the search bar and click on the resulting tile.
183179
184- 4 . In the result page, click on **Enable Integration** which will 
180+ 2 . In the result page, click on **Enable Integration** which will 
185181generate a bearer token as shown below. If Okta is already enabled and 
186182you wish to generate a new token, click **Revoke Token** and reenable 
187183the integration. 
0 commit comments