From 8daa771625ec252cd7b5a4463ebac63a50e1a868 Mon Sep 17 00:00:00 2001 From: Cordis Hall <30606374+cordishall-splunk@users.noreply.github.com> Date: Thu, 14 Nov 2024 12:38:07 -0700 Subject: [PATCH] Update unified-identity.rst --- splunkplatform/unified-id/unified-identity.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/splunkplatform/unified-id/unified-identity.rst b/splunkplatform/unified-id/unified-identity.rst index 62cf9e497..ac39468cc 100644 --- a/splunkplatform/unified-id/unified-identity.rst +++ b/splunkplatform/unified-id/unified-identity.rst @@ -164,7 +164,7 @@ If you already have a Splunk Cloud Platform account and a Splunk Observability C "status": "SUCCESS" -Users will receive an email telling them to authenticate to Splunk Observability Cloud using the new authentication method through Splunk Cloud Platform SSO. Note that users can continue to use their previous login method. If you want to force all users to authenticate through Splunk Cloud Platform SSO, reach out to Splunk Customer Support to deactivate local login. To deactivate login through a third party identity provider, go to :strong:`Data Managemen > Available integrations` in Splunk Observability Cloud, select the appropriate integration (for example, Okta), and select :strong:`Deactivate`. +Users will receive an email telling them to authenticate to Splunk Observability Cloud using the new authentication method through Splunk Cloud Platform SSO. Note that users can continue to use their previous login method. If you want to force all users to authenticate through Splunk Cloud Platform SSO, reach out to Splunk Customer Support to deactivate local login. To deactivate login through a third party identity provider, go to :strong:`Data Management > Available integrations` in Splunk Observability Cloud, select the appropriate integration (for example, Okta), and select :strong:`Deactivate`. .. _unified-id-user-provisioning: