dn: sn=Ellingwood,ou=people,dc=digitalocean,dc=com
This line is called the entry's distinguished name (more on this later) and is used to identify the entry. It functions like a full path back to the root of the DIT. In this instance, we have an entry calledsn=Ellingwood, which we are creating. The direct parent is an entry calledou=peoplewhich is probably being used as a container for entries describing people. The parents of this entry derived from thedigitalocean.comdomain name, which functions as the root of our DIT.Reference: https://www.digitalocean.com/community/tutorials/understanding-the-ldap-protocol-data-hierarchy-and-entry-components LDAP authetication in Splunk in the end is querying a database and this query could be very broad if you don't set the right configurations in authetication.conf In the authetication.conf specification you can find out the following:
userBaseFilter = <string>
* OPTIONAL
* This is the LDAP search filter you wish to use when searching for users.
* Highly recommended, especially when there are many entries in your LDAP
user subtrees
* When used properly, search filters can significantly speed up LDAP queries
* Example that matches users in the IT or HR department:
* userBaseFilter = (|(department=IT)(department=HR))
* See RFC 2254 for more detailed information on search filter syntax
* This defaults to no filtering.
This in turn allows to narrow down the amount of entries that the query needs to search on because it filters allows to look only into certain entries in the user subtrees.用户的userBasefilter如下所示:
userBaseFilter = (|(department=VP30)(department=VPIN)(department=VA02))
观察到此性能缓慢的用户可能不属于原始userBaseFilter中列出的所有部门。删除一个或两个部门,这样每次进行身份验证时,搜索范围会变小,因为LDAP服务器只需要检查一个部门的条目。
| 版本 | 发布日期 | 备注 |
|---|---|---|
1.0 |
28-Sep-2026
|
初始版本 |