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

Commit fbb7249

Browse files
fix
1 parent 6871815 commit fbb7249

File tree

1 file changed

+20
-7
lines changed

1 file changed

+20
-7
lines changed

admin/authentication/authentication-tokens/org-tokens.rst

Lines changed: 20 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -87,20 +87,29 @@ To copy the token value, select :guilabel:`Copy`. You don't need to be an admini
8787
Create an access token
8888
==========================
8989

90-
To create an access token, complete
90+
To get started with creating an access token, follow these steps:
91+
92+
#. Open the Splunk Observability Cloud main menu.
93+
#. Select :menuselection:`Settings` and select :menuselection:`Access Tokens`.
94+
#. Select :guilabel:`New Token`
95+
96+
Next, complete each step in the access token creation guided setup:
97+
98+
* :ref:`create-access-token-name`
99+
* :ref:`create-access-token-permissions`
100+
* :ref:`create-access-token-date`
91101

92102
.. note::
93103

94104
You must be an organization administrator to create access tokens.
95105

106+
.. _create-access-token-name:
107+
96108
#. Name the token and select the authorization scope
97109
-------------------------------------------------------------------------
98110

99111
To get started with creating the token, enter a name and scope for the token. Complete the following steps:
100112

101-
#. Open the Splunk Observability Cloud main menu.
102-
#. Select :menuselection:`Settings` and select :menuselection:`Access Tokens`.
103-
#. Select :guilabel:`New Token`.
104113
#. Enter a unique token name. If you enter a token name that is already in use, even if the token is inactive, Splunk Observability Cloud doesn't accept the name.
105114
#. Select an authorization scope. See the following table for information about the authorization scopes:
106115

@@ -119,20 +128,22 @@ To get started with creating the token, enter a name and scope for the token. Co
119128
* POST :code:`https://ingest.<REALM>.signalfx.com/v2/event`
120129
* POST :code:`https://ingest.<REALM>.signalfx.com/v1/trace`
121130

122-
For information about these endpoints, see :new-page:`Sending data points <https://dev.splunk.com/observability/docs/datamodel/ingest/>`.
131+
For information about these endpoints, see :new-page:`Sending data points <https://dev.splunk.com/observability/docs/datamodel/ingest/>`.
123132
* - API token
124133
- Use this scope to authenticate with Splunk Observability Cloud API endpoints. These endpoints use the following base URLs:
125134

126135
* :code:`https://api.<REALM>.signalfx.com`
127136
* :code:`wss://stream.<REALM>.signalfx.com`
128137

129-
When you create an access token with API authentication scope, select at least one Splunk Observability Cloud role to associate with the token. You can select from ``power``, ``usage``, or ``read_only``. To learn more about Splunk Observability Cloud roles, see :ref:`roles-and-capabilities`.
138+
When you create an access token with API authentication scope, select at least one Splunk Observability Cloud role to associate with the token. You can select from ``power``, ``usage``, or ``read_only``. To learn more about Splunk Observability Cloud roles, see :ref:`roles-and-capabilities`.
130139

131-
For information about these endpoints, see :new-page:`Summary of Splunk Observability Cloud API Endpoints <https://dev.splunk.com/observability/docs/apibasics/api_list/>`.
140+
For information about these endpoints, see :new-page:`Summary of Splunk Observability Cloud API Endpoints <https://dev.splunk.com/observability/docs/apibasics/api_list/>`.
132141

133142
#. (Optional) Add a description for the token.
134143
#. Select :guilabel:`Next` to continue to the next step.
135144

145+
.. _create-access-token-permissions:
146+
136147
#. Determine who can view and use the token
137148
--------------------------------------------------------
138149

@@ -166,6 +177,8 @@ Next, configure token permissions so your organization's users and teams can use
166177

167178
#. Select :guilabel:`Next` to continue to the final step.
168179

180+
.. _create-access-token-date:
181+
169182
#. Configure an expiration date
170183
-----------------------------------------------
171184

0 commit comments

Comments
 (0)