Monitoring Splunk

SAML error or info

dmuruganantham
Engager

The IdP returned role Distinguished Name (DN) 'cn=splunk_dns,ou=groups,dc=foo,dc=bar', which matches configured role map Common Name (CN) splunk_dns'. This role DN has now been locked to the role map CN, using the 'dns' role. Future assertions that contain this CN but do not match the locked DN will be rejected. 

Seeing multiple messages like this, every time we login. Is something wrong with our config? how to stop this notification...

Labels (1)
0 Karma

bnolan
Engager

Hi dmuruganantham,

I think this is expected behavior. We just upgraded our environments (7.3.5 --> 8.1.3) and are now seeing these messages/notifications. Check to see if you have "lockRoleToFullDN=true" set in authentication.conf:

splunk/bin/splunk btool authentication list --debug | grep lockRoleToFullDN

When this parameter is set to true Splunk will capture the full DN of a CN, the first time it sees it, and insert it under the [lockedRoleToFullDNMap_SAML] stanza in etc/system/local/authentication.conf.

I believe you can disable these notifications by setting "lockRoleToFullDN=false". However, I have not tested this just yet.

See documentation here for reference: https://docs.splunk.com/Documentation/Splunk/8.1.3/Admin/Authenticationconf#Security_Assertion_Marku...

 

Regards,

0 Karma
Get Updates on the Splunk Community!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...