<?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: How to integrate SAML authentication for Splunk Cloud? in Security</title>
    <link>https://community.splunk.com/t5/Security/How-to-integrate-SAML-authentication-for-Splunk-Cloud/m-p/276816#M7451</link>
    <description>&lt;P&gt;There is a slight catch with Splunk Cloud that doesn't happen with Splunk Web in my experience. I've set up SAML SSO on both configurations.&lt;/P&gt;

&lt;P&gt;When configuring SAML on Splunk Cloud from Okta was that I needed to configure a load balancer in the SAML configuration. Otherwise it went to sh1.CUSTOMERINSTANCENAME.splunkcloud.com:8443 which isn't Internet accessible.&lt;/P&gt;

&lt;P&gt;Here were my steps (note the missing steps 7-10 that are special for Splunk Cloud since it has a load balancer involved):&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Log into my Splunk Cloud&lt;/LI&gt;
&lt;LI&gt;Go to &lt;STRONG&gt;Settings&lt;/STRONG&gt; | &lt;STRONG&gt;Access Controls&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Set &lt;STRONG&gt;External&lt;/STRONG&gt; to &lt;STRONG&gt;SAML&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Click &lt;STRONG&gt;Configure Splunk to use SAML&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;By Metadata XML File, click Select File and browse to metadata file from Okta&lt;/LI&gt;
&lt;LI&gt;Scroll down and copy Issuer ID and then paste it into the Entity ID field&lt;/LI&gt;
&lt;LI&gt;Scroll down and set Name ID Format to Unspecified&lt;/LI&gt;
&lt;LI&gt;[MISSING STEP] Click the HTTP POST buttons by SSO Binding and SLO Binding&lt;/LI&gt;
&lt;LI&gt;[MISSING STEP] set Fully qualified domain name or IP of the load balancer to &lt;A href="https://CUSTOMERINSTANCENAME.splunkcloud.com"&gt;https://CUSTOMERINSTANCENAME.splunkcloud.com&lt;/A&gt; (replace CUSTOMERINSTANCENAME with yours or your customer's real instance name)&lt;/LI&gt;
&lt;LI&gt;[MISSING STEP] set Redirect port - load balancer port to 443&lt;/LI&gt;
&lt;LI&gt;Click Save&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Thu, 27 Jul 2017 10:00:48 GMT</pubDate>
    <dc:creator>alain_odea</dc:creator>
    <dc:date>2017-07-27T10:00:48Z</dc:date>
    <item>
      <title>How to integrate SAML authentication for Splunk Cloud?</title>
      <link>https://community.splunk.com/t5/Security/How-to-integrate-SAML-authentication-for-Splunk-Cloud/m-p/276814#M7449</link>
      <description>&lt;P&gt;Hi Splunkers,&lt;/P&gt;

&lt;P&gt;I am working on integrating the SAML authentication for Splunk Cloud. I have a few questions before I start working in integration.&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;P&gt;SAML2.0 is pretty standard. What makes Splunk support only specific Identity Providers rather than all the standard SAML2.0 implementations out there?!&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;Does Splunk Cloud support deep link URLs?&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;Which default SAML binding does Splunk require HTTP POST Or REDIRECT Or ARTIFACT?! Does it support other bindings too?&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;How can I get the sp metadata from Splunk Cloud?&lt;/LI&gt;
&lt;/OL&gt;&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Wed, 06 Apr 2016 17:13:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-integrate-SAML-authentication-for-Splunk-Cloud/m-p/276814#M7449</guid>
      <dc:creator>ankumar_juniper</dc:creator>
      <dc:date>2016-04-06T17:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to integrate SAML authentication for Splunk Cloud?</title>
      <link>https://community.splunk.com/t5/Security/How-to-integrate-SAML-authentication-for-Splunk-Cloud/m-p/276815#M7450</link>
      <description>&lt;P&gt;1) SAML2.0 is pretty standard. What makes Splunk support only specific Identity Providers rather than all the standard SAML2.0 implementations out there?!&lt;/P&gt;

&lt;P&gt;Every vendors implement portion of SAML 2.0 and leave out the rest. We need to test / ensure that the IdP works with our code base. This will help us to meet our cloud related SLA to our customers. &lt;/P&gt;

&lt;P&gt;2) Does Splunk Cloud support deep link URLs?&lt;/P&gt;

&lt;P&gt;Yes we do, We track the user’s link(example – a saved search link etc.) using the ‘relayState’ parameter of SAML. When a user logs in using SAML, we sent the user’s link to the IDP as a part of the SAML request in a SP initiated workflow. Once the user is authenticated, we get the relayState back in the SAML response and we redirect the user to the link. &lt;/P&gt;

&lt;P&gt;3) Which default SAML binding does Splunk require HTTP POST Or REDIRECT Or ARTIFACT?! Does it support other bindings too?&lt;/P&gt;

&lt;P&gt;We support POST (6.3/6.4), REDIRECT (6.4.1)&lt;/P&gt;

&lt;P&gt;4)  How can I get the sp metadata from Splunk Cloud?  &lt;/P&gt;

&lt;P&gt;Log in as a local user. Navigate to splunkweb’s endpoint - ‘https://:/en-us/saml/spmetadata' endpoint. This has Splunk’s SP metadata and you can copy the entire xml out. Note:- If saml is not configured, a template entity id called ‘SplunkentityId’ is generated as a placeholder. This entity id can be changed when SAML is configured.&lt;/P&gt;

&lt;P&gt;#thankyoueng&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2016 20:03:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-integrate-SAML-authentication-for-Splunk-Cloud/m-p/276815#M7450</guid>
      <dc:creator>pbrunel_splunk</dc:creator>
      <dc:date>2016-04-13T20:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to integrate SAML authentication for Splunk Cloud?</title>
      <link>https://community.splunk.com/t5/Security/How-to-integrate-SAML-authentication-for-Splunk-Cloud/m-p/276816#M7451</link>
      <description>&lt;P&gt;There is a slight catch with Splunk Cloud that doesn't happen with Splunk Web in my experience. I've set up SAML SSO on both configurations.&lt;/P&gt;

&lt;P&gt;When configuring SAML on Splunk Cloud from Okta was that I needed to configure a load balancer in the SAML configuration. Otherwise it went to sh1.CUSTOMERINSTANCENAME.splunkcloud.com:8443 which isn't Internet accessible.&lt;/P&gt;

&lt;P&gt;Here were my steps (note the missing steps 7-10 that are special for Splunk Cloud since it has a load balancer involved):&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Log into my Splunk Cloud&lt;/LI&gt;
&lt;LI&gt;Go to &lt;STRONG&gt;Settings&lt;/STRONG&gt; | &lt;STRONG&gt;Access Controls&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Set &lt;STRONG&gt;External&lt;/STRONG&gt; to &lt;STRONG&gt;SAML&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Click &lt;STRONG&gt;Configure Splunk to use SAML&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;By Metadata XML File, click Select File and browse to metadata file from Okta&lt;/LI&gt;
&lt;LI&gt;Scroll down and copy Issuer ID and then paste it into the Entity ID field&lt;/LI&gt;
&lt;LI&gt;Scroll down and set Name ID Format to Unspecified&lt;/LI&gt;
&lt;LI&gt;[MISSING STEP] Click the HTTP POST buttons by SSO Binding and SLO Binding&lt;/LI&gt;
&lt;LI&gt;[MISSING STEP] set Fully qualified domain name or IP of the load balancer to &lt;A href="https://CUSTOMERINSTANCENAME.splunkcloud.com"&gt;https://CUSTOMERINSTANCENAME.splunkcloud.com&lt;/A&gt; (replace CUSTOMERINSTANCENAME with yours or your customer's real instance name)&lt;/LI&gt;
&lt;LI&gt;[MISSING STEP] set Redirect port - load balancer port to 443&lt;/LI&gt;
&lt;LI&gt;Click Save&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Thu, 27 Jul 2017 10:00:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-integrate-SAML-authentication-for-Splunk-Cloud/m-p/276816#M7451</guid>
      <dc:creator>alain_odea</dc:creator>
      <dc:date>2017-07-27T10:00:48Z</dc:date>
    </item>
  </channel>
</rss>

