<?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: splunk AD authentication Setup in Security</title>
    <link>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14586#M13652</link>
    <description>&lt;P&gt;It would appear that the baseDN for your users does not contain the "splunkuser".   Supplying your Group and User baseDN settings in addition to the mapped roles would be helpful in solving your problem.   I suggest you check the following as well:&lt;/P&gt;

&lt;P&gt;1 - Does Splunk successfully bind to AD?   If you examine the splunkd.log file, you should see the attempt to bind to the LDAP server.&lt;/P&gt;

&lt;P&gt;2 - Can you browse the LDAP groups on the AD server, while logged in to Splunk Web?   This will confirm if you have configured the groupbaseDN correctly.&lt;/P&gt;

&lt;P&gt;3 - AFTER you mapped an LDAP group to a specific role, are you able to view the users configured?&lt;/P&gt;</description>
    <pubDate>Tue, 01 Jun 2010 22:42:29 GMT</pubDate>
    <dc:creator>Simeon</dc:creator>
    <dc:date>2010-06-01T22:42:29Z</dc:date>
    <item>
      <title>splunk AD authentication Setup</title>
      <link>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14585#M13651</link>
      <description>&lt;P&gt;Trying to Setup Authentication using AD windows 2008,  in way that all the users in the domain will login using their domain ID and password.&lt;/P&gt;

&lt;P&gt;Splunk version Splunk 4.1.2 build 79191&lt;/P&gt;

&lt;P&gt;error : 
ERROR ScopedLDAPConnection - Search for DN 'cn=users,dc=domain,dc=com' gave error: Operations error
ERROR AuthenticationManagerLDAP - Could not find user: splunkuser&lt;/P&gt;

&lt;P&gt;I am able to browse AD with Softerra LDAP Browser  with Bind id and password,and list all the object.&lt;/P&gt;

&lt;P&gt;I have referred to &lt;A href="http://splunkninja.com/video/splunk-ninja-basic-training" rel="nofollow"&gt;http://splunkninja.com/video/splunk-ninja-basic-training&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Any pointers would be appreciated.&lt;/P&gt;

&lt;P&gt;thank you
Newbie&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2010 17:50:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14585#M13651</guid>
      <dc:creator>Newbie</dc:creator>
      <dc:date>2010-06-01T17:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: splunk AD authentication Setup</title>
      <link>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14586#M13652</link>
      <description>&lt;P&gt;It would appear that the baseDN for your users does not contain the "splunkuser".   Supplying your Group and User baseDN settings in addition to the mapped roles would be helpful in solving your problem.   I suggest you check the following as well:&lt;/P&gt;

&lt;P&gt;1 - Does Splunk successfully bind to AD?   If you examine the splunkd.log file, you should see the attempt to bind to the LDAP server.&lt;/P&gt;

&lt;P&gt;2 - Can you browse the LDAP groups on the AD server, while logged in to Splunk Web?   This will confirm if you have configured the groupbaseDN correctly.&lt;/P&gt;

&lt;P&gt;3 - AFTER you mapped an LDAP group to a specific role, are you able to view the users configured?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2010 22:42:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14586#M13652</guid>
      <dc:creator>Simeon</dc:creator>
      <dc:date>2010-06-01T22:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: splunk AD authentication Setup</title>
      <link>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14587#M13653</link>
      <description>&lt;P&gt;Thanks Simeon, Issue i had was related to Binding, so it was bound to LDAP. After I fixed BasedDN everything worked &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2010 18:19:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14587#M13653</guid>
      <dc:creator>Newbie</dc:creator>
      <dc:date>2010-06-02T18:19:23Z</dc:date>
    </item>
    <item>
      <title>Re: splunk AD authentication Setup</title>
      <link>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14588#M13654</link>
      <description>&lt;P&gt;Example authentication.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[authentication]
authSettings = AD
authType = LDAP

[AD]
SSLEnabled = 1
anonymous_referrals = 0
bindDN = batman
bindDNpassword = $1$oX4lsdfsdf899f0s//==
charset = utf8
groupBaseDN = ou=People,ou=Security,dc=gotham,dc=local
groupBaseFilter = (objectClass=group)
groupMappingAttribute = dn
groupMemberAttribute = member
groupNameAttribute = cn
host = batcave01dc02.gotham.city
nestedGroups = 0
network_timeout = 20
port = 636
realNameAttribute = displayname
sizelimit = 1000
timelimit = 15
userBaseDN = OU=People,DC=gotham,DC=local
userBaseFilter = (objectCategory=Person)
userNameAttribute = samaccountname
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You might have namespace conflicts between Splunk users and AD users. Unselect "Splunk" as an authentication option to prevent conflicts.&lt;/P&gt;

&lt;P&gt;No restart of Splunk is needed. Confirm AD groups are seen under Access controls » Authentication method » LDAP strategies » Map Groups. &lt;/P&gt;

&lt;P&gt;To test: 1) map a group to a desired role, then 2) login as a member of the group.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2014 00:37:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunk-AD-authentication-Setup/m-p/14588#M13654</guid>
      <dc:creator>weeb</dc:creator>
      <dc:date>2014-02-12T00:37:41Z</dc:date>
    </item>
  </channel>
</rss>

