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!

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...