Monitoring Splunk

About updating SAML Azure ClientSecret

zapping575
Communicator

We have setup SAML authentication using MS Azure as IDP using the following instructions:

https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/9.3/use-saml-as-an...

Thinking ahead, we would like to document how to renew the clientSecret.

The question is:

When the value for clientSecret requires renewal, can we just add the new value (key value pair), or do we have to revamp/redo the entire Authentication Extensions section? (Script Path, Script Functions, etc...)

Ideally, we are hoping that we can just add the new clientSecret and the platform will take care of it.

Labels (1)
0 Karma
1 Solution

PaulPanther
Motivator

It should be sufficient to simply replace the clientSecret.

View solution in original post

PaulPanther
Motivator

It should be sufficient to simply replace the clientSecret.

zapping575
Communicator

Thanks!

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...