Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 566d3be

Browse files
committed
remove remaining links
1 parent aceef4f commit 566d3be

File tree

4 files changed

+6
-538
lines changed

4 files changed

+6
-538
lines changed

sp-oncall/spoc-integrations/integrations-main.rst

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,6 @@ Splunk On-Call integrations
109109
solarwinds-integration
110110
splunk-integration-guide
111111
splunk-synthetic-monitoring-integration-guide
112-
splunking-victorops-data
113112
statuscast-integration-guide
114113
statushub-integration-guide
115114
statuspage-integration

sp-oncall/spoc-integrations/sensu-integration.rst

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,8 +70,6 @@ Splunk On-Call Handler
7070
#
7171
# Released under the same terms as Sensu (the MIT license); see LICENSE
7272
# for details.
73-
# Downloaded from:
74-
# https://help.victorops.com/knowledge-base/victorops-sensu-integration/#
7573
7674
require 'rubygems' if RUBY_VERSION < '1.9.0'
7775
require 'sensu-handler'

sp-oncall/spoc-integrations/setup-single-sign-on-sso-and-user-provisioning-with-okta-beta.rst

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -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
159155
SSO for your Splunk On-Call organization. Provide the URL link you
160156
copied from the **Identity Provider metadata** from step 7 above and the
161157
list 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

177173
2. Navigate to **Integrations** >> **API**. If API Access is disabled,
178174
click 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
185181
generate a bearer token as shown below. If Okta is already enabled and
186182
you wish to generate a new token, click **Revoke Token** and reenable
187183
the integration.

0 commit comments

Comments
 (0)