Security

Custom sso error page

anoopambli
Communicator

We are using siteminder based sso for our splunk servers (linux). Apache is used as the proxy server. If a user who is not present in slunk or LDAP config he/she gets an error message as below.

"SSO error description
Could not authenticate user via SSO. Please confirm the user set in the http header via your SSO module has a matching splunk account with the same username.
For more help debugging SSO, consult the SSO debug page."

Is there anyway we can customize the error message? by adjusting anything in the apache config?

Tags (1)
0 Karma

martin_mueller
SplunkTrust
SplunkTrust

That message sits in $SPLUNK_HOME/share/splunk/search_mrsparkle/templates/account/sso_error.html, with the appropriate translations for the message IDs in there sitting in Python-2.7/Lib/site-packages/splunk/appserver/mrsparkle/locale/. See http://docs.splunk.com/Documentation/Splunk/6.0.2/AdvancedDev/TranslateSplunk for working with these localization files.

You should be able to make changes to those, just be aware that they probably won't be upgrade-safe.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...