<?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 Using SAML with multiple idP in Security</title>
    <link>https://community.splunk.com/t5/Security/Using-SAML-with-multiple-idP/m-p/476194#M11025</link>
    <description>&lt;P&gt;Currently we are connecting our Splunk Searchheads to our idBroker. The idBroker supports the use of multiple id Providers.&lt;/P&gt;
&lt;P&gt;According to the documentation, Splunk only uses three fields: role, realname and mail.&lt;BR /&gt;(&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.3/Security/ConfigureSSOinSplunkWeb" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.3/Security/ConfigureSSOinSplunkWeb&lt;/A&gt; and&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.3/Admin/Authenticationconf#Authentication_Response_Attribute_Map" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.3/Admin/Authenticationconf#Authentication_Response_Attribute_Map&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;But since we will use multiple idProviders, we will need to map the scSourceIssuer too. &lt;BR /&gt;(&lt;A href="http://schemas.swisscom.com/ws/2019/01/identity/claims/scSourceIssuer=scSourceIssuer" target="_blank"&gt;http://schemas.swisscom.com/ws/2019/01/identity/claims/scSourceIssuer=scSourceIssuer&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;Does anyone know who to solve that?&lt;/P&gt;</description>
    <pubDate>Sun, 07 Jun 2020 17:44:32 GMT</pubDate>
    <dc:creator>markusspitzli</dc:creator>
    <dc:date>2020-06-07T17:44:32Z</dc:date>
    <item>
      <title>Using SAML with multiple idP</title>
      <link>https://community.splunk.com/t5/Security/Using-SAML-with-multiple-idP/m-p/476194#M11025</link>
      <description>&lt;P&gt;Currently we are connecting our Splunk Searchheads to our idBroker. The idBroker supports the use of multiple id Providers.&lt;/P&gt;
&lt;P&gt;According to the documentation, Splunk only uses three fields: role, realname and mail.&lt;BR /&gt;(&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.3/Security/ConfigureSSOinSplunkWeb" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.3/Security/ConfigureSSOinSplunkWeb&lt;/A&gt; and&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.3/Admin/Authenticationconf#Authentication_Response_Attribute_Map" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.3/Admin/Authenticationconf#Authentication_Response_Attribute_Map&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;But since we will use multiple idProviders, we will need to map the scSourceIssuer too. &lt;BR /&gt;(&lt;A href="http://schemas.swisscom.com/ws/2019/01/identity/claims/scSourceIssuer=scSourceIssuer" target="_blank"&gt;http://schemas.swisscom.com/ws/2019/01/identity/claims/scSourceIssuer=scSourceIssuer&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;Does anyone know who to solve that?&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jun 2020 17:44:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Using-SAML-with-multiple-idP/m-p/476194#M11025</guid>
      <dc:creator>markusspitzli</dc:creator>
      <dc:date>2020-06-07T17:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: Using SAML with multiple idP</title>
      <link>https://community.splunk.com/t5/Security/Using-SAML-with-multiple-idP/m-p/532411#M11999</link>
      <description>&lt;P&gt;Request a feature on ideas.splunk.com, asking for support of more than 1 SAML IDP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2020 22:46:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Using-SAML-with-multiple-idP/m-p/532411#M11999</guid>
      <dc:creator>khourihan_splun</dc:creator>
      <dc:date>2020-12-08T22:46:47Z</dc:date>
    </item>
  </channel>
</rss>

