Hello Team,
We are facing an issue with Splunk UI access via SAML SSO and would like your assistance in validating the role/group requirements on the Splunk side.
Users are unable to access the Splunk UI via SAML authentication.
Splunk services and infrastructure are running normally.
SAML response does not contain group information
Hi @sakshi1
As @richgalloway suggested, this sounds like the local role isnt mapped correctly to the SAML role, or it could be that if you've used a Role Alias in the SAML configuration (https://yoursplunkinstance/en-US/manager/launcher/saml/configuration) then it could be using the incorrect role alias.
You might find that using Google Chrome's Developer tool 'SAML' tab is helpful for diagnosing this as you can see the full SAML response which should list the roles. You can then compare the role field name against the SAML Configuration/Alias and the value against the local mapping. Note that sometimes (e.g. Azure/EntraID) it is a role GUID that is presented instead of the friendly name, its this GUID which you will need to map.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
After configuring SAML, did you map group names to Splunk roles? Does your Identity Provider contain group names for each user that will have access to Splunk? Without both of those, Splunk has no way to know what permissions to grant the user.