Most Splunk Cloud deployments integrate with an enterprise Identity Provider (IdP) such as Okta, Microsoft Entra ID, or Ping Identity using SAML 2.0 Single Sign-On (Settings > Authentication Methods > SAML).
During SAML setup, you exchange IdP metadata XML and Splunk Cloud SP metadata, configure attribute aliases (mail, realName, role), and map external IdP groups to Splunk Cloud roles so access changes flow automatically from your directory.
Even with SAML SSO enabled for interactive browser logins, programmatic REST API and ACS integrations rely on Splunk authentication tokens (Bearer JWTs) issued under Settings > Tokens, subject to token expiration and role-based capabilities.
Role Alias: http://schemas.xmlsoap.org/claims/Group
Real Name Alias: displayName
Mail Alias: email
Group Mapping: Splunk_Cloud_Admins -> sc_admin