<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Splunk SSO: server side certificate rotation process in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-SSO-server-side-certificate-rotation-process/m-p/682481#M19020</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Im trying to understand how rotation certificates used for SSO works in a search head cluster. We have a searchhead cluster where we have SSO working already. As for initial setup, I understand we can download SPmetadata.xml file from splunk SAML settings page. However, during rotation, how do we create this as we are using a cert thats already existing and we want to rotate the server side certificate?&lt;/P&gt;&lt;P&gt;If we just download&amp;nbsp;SPmetadata.xml for creating request for IDP, this will have same cert as we are using. If we rotate the cert first at our side so we can download SPmetadata.xml&amp;nbsp; to create request for IDP, then this will end up in error as IDP wont detect server side certificate during this, obviously.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 30 Mar 2024 12:09:21 GMT</pubDate>
    <dc:creator>jpillai</dc:creator>
    <dc:date>2024-03-30T12:09:21Z</dc:date>
    <item>
      <title>Splunk SSO: server side certificate rotation process</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-SSO-server-side-certificate-rotation-process/m-p/682481#M19020</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Im trying to understand how rotation certificates used for SSO works in a search head cluster. We have a searchhead cluster where we have SSO working already. As for initial setup, I understand we can download SPmetadata.xml file from splunk SAML settings page. However, during rotation, how do we create this as we are using a cert thats already existing and we want to rotate the server side certificate?&lt;/P&gt;&lt;P&gt;If we just download&amp;nbsp;SPmetadata.xml for creating request for IDP, this will have same cert as we are using. If we rotate the cert first at our side so we can download SPmetadata.xml&amp;nbsp; to create request for IDP, then this will end up in error as IDP wont detect server side certificate during this, obviously.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 30 Mar 2024 12:09:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-SSO-server-side-certificate-rotation-process/m-p/682481#M19020</guid>
      <dc:creator>jpillai</dc:creator>
      <dc:date>2024-03-30T12:09:21Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk SSO: server side certificate rotation process</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-SSO-server-side-certificate-rotation-process/m-p/683016#M19062</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/48465"&gt;@jpillai&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you have only the option to switch the certificate at the same time on both ends (Splunk &amp;amp; IDP provider).&lt;/P&gt;&lt;P&gt;Just for a certificate replacement you don't need the&amp;nbsp;&lt;SPAN&gt;SPmetadata.xml if the other parameter won't be change.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Create the certificate, hand over the certificate chain to the IDP colleagues, agree a time window for the renewal and then do it.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2024 11:58:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-SSO-server-side-certificate-rotation-process/m-p/683016#M19062</guid>
      <dc:creator>PaulPanther</dc:creator>
      <dc:date>2024-04-03T11:58:49Z</dc:date>
    </item>
  </channel>
</rss>

