https://community.splunk.com/t5/Monitoring-Splunk/About-updating-SAML-Azure-ClientSecret/m-p/757005#M11064 <P>We have setup SAML authentication using MS Azure as IDP using the following instructions:</P><P><A href="https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/9.3/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-authentication-extensions-to-interface-with-your-saml-identity-provider#configure-authentication-extensions-for-microsoft-azure-using-splunk-web-0" target="_blank">https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/9.3/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-authentication-extensions-to-interface-with-your-saml-identity-provider#configure-authentication-extensions-for-microsoft-azure-using-splunk-web-0</A></P><P>Thinking ahead, we would like to document how to renew the clientSecret.</P><P>The question is:</P><P>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...)</P><P>Ideally, we are hoping that we can just add the new clientSecret and the platform will take care of it.</P> Tue, 06 Jan 2026 14:13:39 GMT zapping575 2026-01-06T14:13:39Z https://community.splunk.com/t5/Monitoring-Splunk/About-updating-SAML-Azure-ClientSecret/m-p/757005#M11064 <P>We have setup SAML authentication using MS Azure as IDP using the following instructions:</P><P><A href="https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/9.3/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-authentication-extensions-to-interface-with-your-saml-identity-provider#configure-authentication-extensions-for-microsoft-azure-using-splunk-web-0" target="_blank">https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/9.3/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-authentication-extensions-to-interface-with-your-saml-identity-provider#configure-authentication-extensions-for-microsoft-azure-using-splunk-web-0</A></P><P>Thinking ahead, we would like to document how to renew the clientSecret.</P><P>The question is:</P><P>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...)</P><P>Ideally, we are hoping that we can just add the new clientSecret and the platform will take care of it.</P> Tue, 06 Jan 2026 14:13:39 GMT https://community.splunk.com/t5/Monitoring-Splunk/About-updating-SAML-Azure-ClientSecret/m-p/757005#M11064 zapping575 2026-01-06T14:13:39Z https://community.splunk.com/t5/Monitoring-Splunk/About-updating-SAML-Azure-ClientSecret/m-p/758495#M11084 <P>It should be sufficient to simply replace the clientSecret.</P> Thu, 19 Feb 2026 08:32:44 GMT https://community.splunk.com/t5/Monitoring-Splunk/About-updating-SAML-Azure-ClientSecret/m-p/758495#M11084 PaulPanther 2026-02-19T08:32:44Z https://community.splunk.com/t5/Monitoring-Splunk/About-updating-SAML-Azure-ClientSecret/m-p/758497#M11085 <P>Thanks!</P> Thu, 19 Feb 2026 09:10:57 GMT https://community.splunk.com/t5/Monitoring-Splunk/About-updating-SAML-Azure-ClientSecret/m-p/758497#M11085 zapping575 2026-02-19T09:10:57Z