⛏️GetSplunky!
Lv.1Intern
0 XP
0
Home Map Stats Drill Board Log In
CoursesArticlesSPL Cheat SheetCertification PathAboutPrivacyTerms

Splunky is an independent, free study resource. It is not affiliated with, endorsed by, or sponsored by Splunk or Cisco. Splunk, SPL and related marks are trademarks of Splunk, a Cisco company, and are used here only to identify the certifications this site helps you study for.

© 2026 Splunky

Back to Floor
The Access Bastion • Room 3

SAML SSO, Role Mapping & Auth Tokens

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.

Required SAML attribute mapping concepts
Role Alias: http://schemas.xmlsoap.org/claims/Group
Real Name Alias: displayName
Mail Alias: email
Group Mapping: Splunk_Cloud_Admins -> sc_admin
Keep one local sc_admin break-glass account documented in a secure vault in case your IdP SAML certificate expires and locks out SSO logins.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Complete the Splunk Cloud authentication and authorization rules.
Enterprise SSO maps IdP groups to Splunk Cloud roles such as using 2.0 metadata, while automated API and ACS workflows authenticate with Bearer tokens and row-level search restrictions use .