<?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: Active Directory nested groups in Security</title>
    <link>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82963#M2745</link>
    <description>&lt;P&gt;Glad to hear it worked out!&lt;/P&gt;</description>
    <pubDate>Mon, 08 Oct 2012 14:54:57 GMT</pubDate>
    <dc:creator>dart</dc:creator>
    <dc:date>2012-10-08T14:54:57Z</dc:date>
    <item>
      <title>Active Directory nested groups</title>
      <link>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82960#M2742</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I understand that Splunk 4.3.3 should support nested groups in Active Directory, according to &lt;A href="http://blogs.splunk.com/2012/02/23/splunk-and-nested-groups-for-authorization/"&gt;this document&lt;/A&gt;. However, I'm unable to get it working. I have set &lt;CODE&gt;nestedGroups=1&lt;/CODE&gt;. I've also set &lt;CODE&gt;groupMemberAttribute=member&lt;/CODE&gt;, (and tried without it as well), but it still won't work.&lt;/P&gt;

&lt;P&gt;Currently, I'm only testing this with one nested group.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;CN=it-infrastructure,OU=SPLUNK,OU=Application Groups,OU=Groups,DC=company,DC=domain,DC=tld&lt;/CODE&gt; &lt;/P&gt;

&lt;P&gt;which has a member:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;CN=infrastructure-internal,OU=Organisational Groups,OU=Managed Groups,OU=Groups,DC=company,DC=domain,DC=tld&lt;/CODE&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# authentication.conf:
[AD]
SSLEnabled = 0
anonymous_referrals = 1
bindDN = cn=svc-splunk-01,ou=Splunk,ou=Service Accounts,ou=Other Accounts,dc=company,dc=domain,dc=tld
bindDNpassword = snafu
charset = utf8
dynamicMemberAttribute = member
groupBaseDN = ou=SPLUNK,ou=Application Groups,ou=Groups,dc=company,dc=domain,dc=tld
groupBaseFilter = (objectclass=*)
groupMappingAttribute = dn
groupMemberAttribute = member
groupNameAttribute = cn
host = ldap.company.domain.tld
nestedGroups = 1
network_timeout = 20
port = 389
realNameAttribute = cn
sizelimit = 1000
timelimit = 15
userBaseDN = ou=Departments,dc=company,dc=domain,dc=tld
userBaseFilter = (objectclass=*)
userNameAttribute = samaccountname
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Now looking at the configuration, I'm wondering if the problem may be the &lt;CODE&gt;groupBaseDN&lt;/CODE&gt; setting. This matches the parent group, but not the nested group. Is this the problem? If I widen it to just &lt;CODE&gt;ou=Groups,dc=...&lt;/CODE&gt;, I get 1000+ groups, which is quite a lot, but I'm not sure if it's a problem. So, does the nested group also have to match the groupBaseDN?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2012 08:30:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82960#M2742</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2012-10-08T08:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory nested groups</title>
      <link>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82961#M2743</link>
      <description>&lt;P&gt;Widen the &lt;CODE&gt;groupBaseDN&lt;/CODE&gt; - it shouldn't be a problem. If you're worried, add to the &lt;CODE&gt;groupBaseFilter&lt;/CODE&gt; to just look at those in the right OUs.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2012 13:59:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82961#M2743</guid>
      <dc:creator>dart</dc:creator>
      <dc:date>2012-10-08T13:59:40Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory nested groups</title>
      <link>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82962#M2744</link>
      <description>&lt;P&gt;Thanks!&lt;BR /&gt;
Yes, I was worried about the amount of groups listed and I tried out several combinations of values for &lt;CODE&gt;groupBaseFilter&lt;/CODE&gt; and &lt;CODE&gt;dynamicGroupFilter&lt;/CODE&gt;. Either I couldn't get it to authenticate or the list of groups.&lt;/P&gt;

&lt;P&gt;Thanks to your suggestion, I set both to the same value and it does work. Authentication works and the list is nice and small, so thank you very much!&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2012 14:43:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82962#M2744</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2012-10-08T14:43:07Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory nested groups</title>
      <link>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82963#M2745</link>
      <description>&lt;P&gt;Glad to hear it worked out!&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2012 14:54:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Active-Directory-nested-groups/m-p/82963#M2745</guid>
      <dc:creator>dart</dc:creator>
      <dc:date>2012-10-08T14:54:57Z</dc:date>
    </item>
  </channel>
</rss>

