Skip to content

Commit 0ed47e3

Browse files
Merge pull request #2547 from splunk/tcarter-O11YDOCS-6874-curlCommands
tcarter-O11YDOCS-6874-curlCommands
2 parents b91b26f + 60d3adc commit 0ed47e3

File tree

1 file changed

+13
-18
lines changed

1 file changed

+13
-18
lines changed

splunkplatform/unified-id/unified-identity.rst

Lines changed: 13 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ If you already have a Splunk Cloud Platform account and a Splunk Observability C
105105

106106
a. To pair with command-line interface, enter the following Admin Config Services (ACS) command:
107107

108-
.. code-block:: bash
108+
.. code-block:: bash
109109
110110
acs observability pair --o11y-access-token "<enter-o11y-access-token>"
111111
@@ -123,38 +123,33 @@ If you already have a Splunk Cloud Platform account and a Splunk Observability C
123123

124124
.. code-block:: bash
125125
126-
curl --location
127-
'https://admin.splunk.com/<enter-stack-name>/adminconfig/v2/observability/sso-pairing' \
128-
--header 'Content-Type: application/json' \
129-
--header 'Authorization: Bearer <enter-splunk-admin-api-token>' \
130-
--header 'o11y-access-token': '<enter-o11y-api-token>'
131-
126+
curl -X POST 'https://admin.splunk.com/<enter-stack-name>/adminconfig/v2/observability/sso-pairing' \
127+
-H "Content-Type: application/json" \
128+
-H "Authorization: Bearer <enter-splunk-admin-api-token>" \
129+
-H "o11y-access-token: <enter-o11y-api-token>"
132130
133-
Whether you used the command-line interface or API endpoints, the pairing command returns a pairing id:
131+
Whether you used the command-line interface or API endpoints, the pairing command returns a pairing id:
134132

135-
.. code-block:: bash
133+
.. code-block:: bash
136134
137-
"id": "<pairing-id>"
135+
"id": "<pairing-id>"
138136
139137
4. You can use the pairing id to get the current status of the pairing.
140138

141-
a. To get the status using command-line interface, run the following ACS command:
139+
a. To get the status using command-line interface, run the following ACS command then replace the pairing id and the access token with your own values:
142140

143141
.. code-block:: bash
144142
145143
acs observability pairing-status-by-id --pairing-id "<enter-pairing-id>" --o11y-access-token "<enter-o11y-access-token>"
146-
147-
Replace the pairing id and the access token with your own values.
148144
149145
b. To get the status using API endpoints, run the following curl command with the data you obtained in step 3b:
150146

151147
.. code-block:: bash
152148
153-
curl --location --request GET
154-
'https://admin.splunk.com/<enter-stack-name>/adminconfig/v2/observability/sso-pairing/<enter-pairing-id>' \
155-
--header 'Content-Type: application/json' \
156-
--header 'Authorization: Bearer <enter-splunk-admin-api-token>'
157-
--header 'o11y-access-token': '<enter-o11y-api-token>'
149+
curl -X GET 'https://admin.splunk.com/<enter-stack-name>/adminconfig/v2/observability/sso-pairing/<enter-pairing-id>' \
150+
-H "Content-Type: application/json" \
151+
-H "Authorization: Bearer <enter-splunk-admin-api-token>" \
152+
-H "o11y-access-token: <enter-o11y-api-token>"
158153
159154
5. The system returns a status message showing whether or not the pairing was a success. Statuses are SUCCESS, FAILED, or IN_PROGRESS.
160155

0 commit comments

Comments
 (0)