Splunk Enterprise

native saml auth with shibboleth

sheon
Observer

we've ran into two odd issues when testing a Shibboleth implementation, but I'm not sure if they are related. AQRs are setup so users are not cached, we noticed that a user without content only show on a search head the load balancer has sent them to and therefore content cannot be assigned to them unless they've accessed all the search heads.

along the content line, replicate certificates does not do what it says. it does not replicate the idp cert across the search heads, but as soon as that was enabled does content, users, and saml groups replicate peer-to-peer. I assume we have an incorrect setting in place, but any help is very much appreciated!

Labels (2)
Tags (3)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...