<?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 Re: SAML SSO on Splunkv8.2.4 in Security</title>
    <link>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/585056#M15913</link>
    <description>&lt;P&gt;Please check with Splunk support once.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Feb 2022 05:28:44 GMT</pubDate>
    <dc:creator>VatsalJagani</dc:creator>
    <dc:date>2022-02-15T05:28:44Z</dc:date>
    <item>
      <title>SAML SSO on Splunkv8.2.4</title>
      <link>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/584576#M15893</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Any changes happened on SAML SSO configuration in the new Splunk v8.2.4 ?&lt;/P&gt;&lt;P&gt;We have an IdP configured to use SSO and it is working in the Splunk v8.1.1. We recently upgraded to v8.2.4 we copied the same authentication.conf from v8.1.1.&amp;nbsp; Seeing the below error in the Splunkd.log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;relaystate is empty&lt;/P&gt;&lt;P&gt;RelayState may be missing due to IDP-intiated SAML workflow.&lt;/P&gt;&lt;P&gt;User=&amp;lt;user&amp;gt;@&amp;lt;DOMAIN1.DOMAIN.COM&amp;gt; domain= does not match default domain. Contact your syste administrator for more information about the default domain=saml for this system&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea how to fix this error?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2022 18:46:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/584576#M15893</guid>
      <dc:creator>shangshin</dc:creator>
      <dc:date>2022-02-10T18:46:39Z</dc:date>
    </item>
    <item>
      <title>Re: SAML SSO on Splunkv8.2.4</title>
      <link>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/584635#M15894</link>
      <description>&lt;P&gt;Have you upgraded or copied the authentication.conf to a new instance?&lt;/P&gt;&lt;P&gt;If you copied to a new instance you have to make sure you write all passwords in clear text and restart Splunk.&lt;/P&gt;&lt;P&gt;Also, if this is a new system check from the SAML side that nothing is blocking due to filters.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Feb 2022 05:22:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/584635#M15894</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2022-02-11T05:22:03Z</dc:date>
    </item>
    <item>
      <title>Re: SAML SSO on Splunkv8.2.4</title>
      <link>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/585024#M15912</link>
      <description>&lt;P&gt;We got the saml sso working on v8.1.1 and when we migrated to v8.2.4 it works fine.&lt;/P&gt;&lt;P&gt;However,&amp;nbsp; on the fresh install of v8.2.4 we are getting the same error. I tried rrestarting by eplacing the sslpassword with cleartext, It is not fixing the issue. Still the same errot&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 18:43:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/585024#M15912</guid>
      <dc:creator>shangshin</dc:creator>
      <dc:date>2022-02-14T18:43:08Z</dc:date>
    </item>
    <item>
      <title>Re: SAML SSO on Splunkv8.2.4</title>
      <link>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/585056#M15913</link>
      <description>&lt;P&gt;Please check with Splunk support once.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 05:28:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SAML-SSO-on-Splunkv8-2-4/m-p/585056#M15913</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2022-02-15T05:28:44Z</dc:date>
    </item>
  </channel>
</rss>

