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

Commit 42af567

Browse files
Merge pull request #1700 from brittonjohnson/patch-12
Update unified-identity.rst
2 parents 9f27ebe + 0cba5f7 commit 42af567

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

splunkplatform/unified-id/unified-identity.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -180,6 +180,10 @@ In Splunk Cloud Platform, create the custom role ``o11y_access`` and assign it t
180180

181181
.. note:: If you do not create and assign the custom role ``o11y_access``, users receive the following error message when trying to log in to Splunk Observability Cloud: "You do not have access to Splunk Observability Cloud. Contact your Splunk Cloud Platform administrator for assistance."
182182

183+
NOTE: When a new user from Splunk Support is added to your organization for troubleshooting an issue, they will appear as int_* in your organization. This is normal and is not an issue and is not a bug but a feature of Unified Identity. They will all normally have the same IP Address as well, since they are on a VPN.
184+
185+
186+
183187
If the user does not exist in Splunk Observability Cloud, the integration automatically creates a user in Splunk Observability Cloud and maps Splunk Cloud Platform roles to the following Splunk Observability Cloud roles:
184188

185189
.. list-table::

0 commit comments

Comments
 (0)