<?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 ldap in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168043#M4970</link>
    <description>&lt;P&gt;I could do it myself changed the Group mapping attribute to dn instead of memberof and now I could login with the LDAP credentials.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Mar 2014 06:41:00 GMT</pubDate>
    <dc:creator>sushma6</dc:creator>
    <dc:date>2014-03-04T06:41:00Z</dc:date>
    <item>
      <title>Splunk ldap</title>
      <link>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168038#M4965</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am trying to integrate Splunk with Ldap, and hence I entered the following set of information.&lt;/P&gt;

&lt;P&gt;LDAP Strategy Name: ldap&lt;BR /&gt;
Host: 192.127.44.155&lt;BR /&gt;
Port: 389&lt;BR /&gt;
Bind DN: CN=va230033,OU=Application Accounts,DC=corp,DC=ncr,DC=com&lt;BR /&gt;
Bind DN password: xxxxxx&lt;BR /&gt;
User base DN: dc=corp,dc=ncr,dc=com&lt;BR /&gt;
User name attribute: samaccountname&lt;BR /&gt;
Real name attribute: displayname&lt;BR /&gt;
Group mapping attribute: dn&lt;BR /&gt;
Group base DN: dc=corp,dc=ncr,dc=com&lt;BR /&gt;
Group name attribute: cn&lt;BR /&gt;
Static member attribute: member&lt;/P&gt;

&lt;P&gt;When i created a ldap with the above settings, i received the following error: ldap server warning: size limi exceeded. Not only this once done, when I try to map groups i could not find the groups that I want. So as to make search more refinable, I even  included the following filter: (&amp;amp;(objectCategory=group) (cn=sweng*)) under User base filter.&lt;/P&gt;

&lt;P&gt;Doing so did not help me, still I could not retrieve the group that I require and still the error persists.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Sushma.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Feb 2014 10:28:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168038#M4965</guid>
      <dc:creator>sushma6</dc:creator>
      <dc:date>2014-02-27T10:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ldap</title>
      <link>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168039#M4966</link>
      <description>&lt;P&gt;How about increasing the size of this parameter? &lt;BR /&gt;
Advanced settings -&amp;gt; Search request size limit&lt;/P&gt;

&lt;P&gt;•Search request size limit &lt;BR /&gt;
◦To avoid performance-related issues, you can set the search request size limit. Splunk will then request that the LDAP server return the specified maximum number of entries in response to a search request. In a large deployment with millions of users, setting this limit to a high value could result in a long response, depending on the search filter set in the LDAP strategy configuration. If this limit is reached, splunkd.log should contain a size limit exceeded message. &lt;BR /&gt;
◦You should set the search request time limit and search request size limit values in conjunction with the splunkweb timeout property, described in "Configure user session timeouts". If you have a group that is not showing up in the Splunk console, it was likely excluded due to one of these limits. Tune these properties as needed. &lt;BR /&gt;
◦To set the request size limit higher than 1000, you must also edit max_users_to_precache in limits.conf to accomodate the number of users you set for your request size limit. &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.2/Security/ConfigureLDAPwithSplunkWeb" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.2/Security/ConfigureLDAPwithSplunkWeb&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:59:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168039#M4966</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2020-09-28T15:59:34Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ldap</title>
      <link>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168040#M4967</link>
      <description>&lt;P&gt;Yes,now i am able to view the groups that I required, but not able to login to the SPLUNK using the users belonging to that group. Is there anything else that I need to do?&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 12:32:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168040#M4967</guid>
      <dc:creator>sushma6</dc:creator>
      <dc:date>2014-02-28T12:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ldap</title>
      <link>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168041#M4968</link>
      <description>&lt;P&gt;You need to be added to the group (user role, for example) role with login privileges.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 16:17:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168041#M4968</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2014-02-28T16:17:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ldap</title>
      <link>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168042#M4969</link>
      <description>&lt;P&gt;yes after mapping the group, I assigned admin role to all the users in that group, there are 10 users in that group and I gave each of them admin rights, even i am included in that group. Once done i tried to login with the LDAP credentials, but it is showing as Invalid username and password.&lt;/P&gt;</description>
      <pubDate>Sun, 02 Mar 2014 15:06:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168042#M4969</guid>
      <dc:creator>sushma6</dc:creator>
      <dc:date>2014-03-02T15:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ldap</title>
      <link>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168043#M4970</link>
      <description>&lt;P&gt;I could do it myself changed the Group mapping attribute to dn instead of memberof and now I could login with the LDAP credentials.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2014 06:41:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-ldap/m-p/168043#M4970</guid>
      <dc:creator>sushma6</dc:creator>
      <dc:date>2014-03-04T06:41:00Z</dc:date>
    </item>
  </channel>
</rss>

