After upgrading to the latest Splunk version (9.2.1) admin users were unable to log in to the UI. The following message appeared:
No valid Splunk role found in local mapping.
Version 9.0.5 was running in the environment prior to the upgrade to 9.2.1 and admin roles for admin users were working as expected.
Most internal users were able to log in to the Splunk UI, but all admins were facing the issue.
The environment is using a SAML server which is implemented with Splunk, and it was configured correctly. No logs showing errors appeared regarding the admin roles in splunkd.log. After checking authentication.conf it was found that the admin role was not mapped.
In the Splunk documentation version 9.0.5 there are no defaults for the excludedAutoMappedRoles.
excludedAutoMappedRoles = <comma separated list>
* Comma separated list of Splunk roles that should be prevented
from being auto-mapped by Splunk from the IDP Response.
* This setting is optional.
* No default.
In the Splunk documentation version 9.2.1 the excludedAutoMappedRoles are working differently. The default roles are admin and power, which means that these roles are not being mapped like in previous versions.
excludedAutoMappedRoles = <comma separated list>
* A list of Splunk roles for which the Splunk platform is not to
auto-map from the identity provider response.
* This setting is optional.
* Default: admin, power
To solve this issue add the following if upgrading from previous Splunk versions to the latest and the admin role will be mapped again. In the authentication.conf file add:
[roleMap_SAML]
admin = <SAML_group>
[roleMap_SAML]
admin = admin
./splunk restart
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |