<?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: SHC with SAML authentication - role update on existing group does not apply in Security</title>
    <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373110#M9203</link>
    <description>&lt;P&gt;As explained above, this part works fine... group list is properly communicated through SAML answer (I did use similar plugin to the one you suggest to confirm that)... My problem is for the next role update... For unknow reason, it does not look to be taken into account. And I am not sure what are the constraints (do we need to restart the all SHC members to refresh the role config ? do we need impacted users to explicitly logout, etc.)&lt;/P&gt;</description>
    <pubDate>Thu, 29 Jun 2017 14:11:54 GMT</pubDate>
    <dc:creator>sylbaea</dc:creator>
    <dc:date>2017-06-29T14:11:54Z</dc:date>
    <item>
      <title>SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373103#M9196</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have a Search Head Cluster configured with SAML authentication (ADFS)... &lt;BR /&gt;
For an existing SAML group (already granted with some role), adding new roles  using GUI does not apply.&lt;/P&gt;

&lt;P&gt;For instance I have a user &lt;STRONG&gt;user1&lt;/STRONG&gt; member of SAML group &lt;STRONG&gt;group1&lt;/STRONG&gt;.&lt;BR /&gt;
And I have several roles &lt;STRONG&gt;app1&lt;/STRONG&gt;, &lt;STRONG&gt;app2&lt;/STRONG&gt;, &lt;STRONG&gt;app3&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;I initially grant the user with role &lt;STRONG&gt;app1&lt;/STRONG&gt;... Looking at &lt;STRONG&gt;authentication.conf&lt;/STRONG&gt;, I see:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[userToRoleMap_SAML]
user1@domain.com = app1

[roleMap_SAML]
app1 = group1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;For this first test, access to &lt;STRONG&gt;app1&lt;/STRONG&gt; is ok for &lt;STRONG&gt;user1&lt;/STRONG&gt;... Also I already noticed that the role group assignment has been copied to the user... Strange but so far, it does not create a real problem.&lt;/P&gt;

&lt;P&gt;But then if I edit again group role assignment to add more roles. This time, I get:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[userToRoleMap_SAML]
user1@domain.com = app1

[roleMap_SAML]
app1 = group1
app2 = group1
app3 = group1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;roleMap_SAML&lt;/STRONG&gt; is updated as expected, but this time, no copy-paste to the user section.&lt;BR /&gt;
And the roles are never really granted to the user including after a rolling restart.&lt;BR /&gt;
I checked the value of roles using &lt;STRONG&gt;"| rest splunk_server=local /services/authentication/current-context "&lt;/STRONG&gt; and I only see the role defined by user mapping.&lt;/P&gt;

&lt;P&gt;Why does the group mapping does not work ?&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 10:57:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373103#M9196</guid>
      <dc:creator>sylbaea</dc:creator>
      <dc:date>2017-06-28T10:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373104#M9197</link>
      <description>&lt;P&gt;I need some clarification...  Are you trying to login through ADFS as user1 and your problem is that this user is not being given the app2 and app3 role in splunk?&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 20:38:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373104#M9197</guid>
      <dc:creator>suarezry</dc:creator>
      <dc:date>2017-06-28T20:38:15Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373105#M9198</link>
      <description>&lt;P&gt;yes, this is my problem.&lt;BR /&gt;
In the meantime, I found old discussions here about same problem. It was stated that we cannot have both SSO with SAML and role group remapping working... Does this limitation still exist ?&lt;BR /&gt;
In same discussions, it was also suggested to create roles directly matching AD groups. I have not tried that yet but ideally I would like to be able to maintain my own naming convention for roles in Splunk.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 01:33:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373105#M9198</guid>
      <dc:creator>sylbaea</dc:creator>
      <dc:date>2017-06-29T01:33:21Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373106#M9199</link>
      <description>&lt;P&gt;I do not believe that this limitation exists. What version are you running?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 12:56:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373106#M9199</guid>
      <dc:creator>brreeves_splunk</dc:creator>
      <dc:date>2017-06-29T12:56:43Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373107#M9200</link>
      <description>&lt;P&gt;Ok, so your first step is to find out what role information ADFS releasing to you, to pass to splunk.  Use a browser plugin to trace your saml messages:&lt;BR /&gt;
&lt;A href="https://addons.mozilla.org/en-US/firefox/addon/saml-tracer/"&gt;https://addons.mozilla.org/en-US/firefox/addon/saml-tracer/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;What is the role information in the ADFS assertion?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:06:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373107#M9200</guid>
      <dc:creator>suarezry</dc:creator>
      <dc:date>2017-06-29T14:06:27Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373108#M9201</link>
      <description>&lt;P&gt;6.5.3 (Windows)&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:08:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373108#M9201</guid>
      <dc:creator>sylbaea</dc:creator>
      <dc:date>2017-06-29T14:08:17Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373109#M9202</link>
      <description>&lt;P&gt;Based on the configuration, as long as user1 is a member of group1, they should receive those permissions as well as their userToRoleMap permissions.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:11:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373109#M9202</guid>
      <dc:creator>brreeves_splunk</dc:creator>
      <dc:date>2017-06-29T14:11:23Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373110#M9203</link>
      <description>&lt;P&gt;As explained above, this part works fine... group list is properly communicated through SAML answer (I did use similar plugin to the one you suggest to confirm that)... My problem is for the next role update... For unknow reason, it does not look to be taken into account. And I am not sure what are the constraints (do we need to restart the all SHC members to refresh the role config ? do we need impacted users to explicitly logout, etc.)&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:11:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373110#M9203</guid>
      <dc:creator>sylbaea</dc:creator>
      <dc:date>2017-06-29T14:11:54Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373111#M9204</link>
      <description>&lt;P&gt;This would be good to confirm that it is returning the group we think it is (group1) so that we're sure it SHOULD be applying that role to user1.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:12:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373111#M9204</guid>
      <dc:creator>brreeves_splunk</dc:creator>
      <dc:date>2017-06-29T14:12:12Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373112#M9205</link>
      <description>&lt;P&gt;You do need to do an Authentication Refresh under Settings &amp;gt; Authentication Method at the bottom.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:12:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373112#M9205</guid>
      <dc:creator>brreeves_splunk</dc:creator>
      <dc:date>2017-06-29T14:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373113#M9206</link>
      <description>&lt;P&gt;Ok...&lt;BR /&gt;
If you have confirmed that ADFS is passing the correct role information with a browser plugin then your next step is to look at $SPLUNK_HOME/var/log/splunk/splunkd.log for any SAML related errors or warnings.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:16:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373113#M9206</guid>
      <dc:creator>suarezry</dc:creator>
      <dc:date>2017-06-29T14:16:32Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373114#M9207</link>
      <description>&lt;P&gt;Thanks ! I missed that button... It does resolve my concern... This being said, I do not remember it was advised to use this button in the documentation... Maybe I missed it too.&lt;BR /&gt;
Thanks a lot.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:24:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373114#M9207</guid>
      <dc:creator>sylbaea</dc:creator>
      <dc:date>2017-06-29T14:24:09Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373115#M9208</link>
      <description>&lt;P&gt;you may want to put your comment as an answer.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:24:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373115#M9208</guid>
      <dc:creator>sylbaea</dc:creator>
      <dc:date>2017-06-29T14:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373116#M9209</link>
      <description>&lt;P&gt;Done. Please upvote for exposure. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; (yay fake internet points!)&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:26:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373116#M9209</guid>
      <dc:creator>brreeves_splunk</dc:creator>
      <dc:date>2017-06-29T14:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373117#M9210</link>
      <description>&lt;P&gt;@brreeves&lt;BR /&gt;
I am facing the same issue, after removing the user from SAML portal, the user remains in the authentication.conf, however he is not able to login. How do I address this concern ?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jul 2018 14:17:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373117#M9210</guid>
      <dc:creator>sidhantbhayana</dc:creator>
      <dc:date>2018-07-20T14:17:11Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373118#M9211</link>
      <description>&lt;P&gt;@sidhantbhayana if you remove them from the SAML IdP, they will no longer have access. Authentication.conf is what gets applied after they are approved by the IdP.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jul 2018 22:38:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373118#M9211</guid>
      <dc:creator>brreeves_splunk</dc:creator>
      <dc:date>2018-07-20T22:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373119#M9212</link>
      <description>&lt;P&gt;@sylbaea - I am strugging with setting up Splunk SHC to work with ADFS (all internal) ... any chance you can share any info?&lt;/P&gt;

&lt;P&gt;I have a F5 LB VIP (no SSL) - call this  &lt;A href="https://splunk:443"&gt;https://splunk:443&lt;/A&gt; that points to 3 SHC members (call this  &lt;A href="https://splunk1:8000"&gt;https://splunk1:8000&lt;/A&gt; , &lt;A href="https://splunk2:8000"&gt;https://splunk2:8000&lt;/A&gt;, &lt;A href="https://splunk3:8000"&gt;https://splunk3:8000&lt;/A&gt;)&lt;/P&gt;

&lt;P&gt;Each of the splunk cluster members - have the same "ssl certificate" with CN = splunk  (Custom CA signed cert)&lt;/P&gt;

&lt;P&gt;I am struggling to follow steps on &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.4/Security/SAMLSHC"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.4/Security/SAMLSHC&lt;/A&gt;  .....&lt;/P&gt;

&lt;P&gt;Any help would be great! &lt;/P&gt;</description>
      <pubDate>Tue, 26 Feb 2019 22:12:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/373119#M9212</guid>
      <dc:creator>deepamshah</dc:creator>
      <dc:date>2019-02-26T22:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: SHC with SAML authentication - role update on existing group does not apply</title>
      <link>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/692633#M17965</link>
      <description>&lt;P&gt;I have added a New SAML group from our organisation Azure AD and assigned a role which was created before with limited privileges/capabilities and access to only 2 indexes. However, users in that group have reported being unable to access the resources. Upon verifying in the users section of Splunk Cloud settings, I noticed that the specific users involved in that group were not assigned their roles. Is there a troubleshooting step I should take? I noticed an option in the SAML settings to reload the SAML configuration, but I am hesitant to click on it.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 11:58:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/SHC-with-SAML-authentication-role-update-on-existing-group-does/m-p/692633#M17965</guid>
      <dc:creator>roshanadabala</dc:creator>
      <dc:date>2024-07-08T11:58:49Z</dc:date>
    </item>
  </channel>
</rss>

