<?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 LDAP groups do not get replicated between search heads in a cluster in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/LDAP-groups-do-not-get-replicated-between-search-heads-in-a/m-p/520661#M3500</link>
    <description>&lt;P&gt;Hi, Rony here.&lt;BR /&gt;&lt;BR /&gt;We've got a Search Head Cluster with 6 Search Heads.&lt;BR /&gt;When a user access our splunk URL, it hits a load balancer, wich randomly uses one of the 6 Search heads.&lt;BR /&gt;Authentication is by LDAP integration.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Heres the problem:&lt;BR /&gt;When a user logins to splunk, that user groups (and as a result, his roles) only gets updated on the specific search head that user happens to hit.&lt;BR /&gt;If the user continues to use splunk, the load balancer might connect him to another search head, where the user groups are not updated&lt;BR /&gt;The user tries to perform an action that requires the permissions provided by the group, and fails.&lt;BR /&gt;&lt;BR /&gt;Is there a way that, when the user logs in, his assigned LDAP groups gets replicated to all the search heads on the cluster?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 21 Sep 2020 16:05:54 GMT</pubDate>
    <dc:creator>tqi_raurora</dc:creator>
    <dc:date>2020-09-21T16:05:54Z</dc:date>
    <item>
      <title>LDAP groups do not get replicated between search heads in a cluster</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/LDAP-groups-do-not-get-replicated-between-search-heads-in-a/m-p/520661#M3500</link>
      <description>&lt;P&gt;Hi, Rony here.&lt;BR /&gt;&lt;BR /&gt;We've got a Search Head Cluster with 6 Search Heads.&lt;BR /&gt;When a user access our splunk URL, it hits a load balancer, wich randomly uses one of the 6 Search heads.&lt;BR /&gt;Authentication is by LDAP integration.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Heres the problem:&lt;BR /&gt;When a user logins to splunk, that user groups (and as a result, his roles) only gets updated on the specific search head that user happens to hit.&lt;BR /&gt;If the user continues to use splunk, the load balancer might connect him to another search head, where the user groups are not updated&lt;BR /&gt;The user tries to perform an action that requires the permissions provided by the group, and fails.&lt;BR /&gt;&lt;BR /&gt;Is there a way that, when the user logs in, his assigned LDAP groups gets replicated to all the search heads on the cluster?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Sep 2020 16:05:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/LDAP-groups-do-not-get-replicated-between-search-heads-in-a/m-p/520661#M3500</guid>
      <dc:creator>tqi_raurora</dc:creator>
      <dc:date>2020-09-21T16:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP groups do not get replicated between search heads in a cluster</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/LDAP-groups-do-not-get-replicated-between-search-heads-in-a/m-p/520761#M3537</link>
      <description>&lt;P&gt;How did you update LDAP configurations on search heads are in cluster?&lt;/P&gt;&lt;P&gt;Did you update LDAP groups from Search head CLI? if you have updated from search web, ideally this should get replicated to all search members part of cluster.&lt;/P&gt;&lt;P&gt;and also, once you make change from splunk search member GUI, verify the change in another search member.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Sep 2020 09:03:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/LDAP-groups-do-not-get-replicated-between-search-heads-in-a/m-p/520761#M3537</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2020-09-22T09:03:09Z</dc:date>
    </item>
  </channel>
</rss>

