[
https://issues.apache.org/jira/browse/OPENMEETINGS-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051508#comment-14051508
]
Roberto E.L. commented on OPENMEETINGS-1033:
--------------------------------------------
The fix worked!.
Thank you Maxim.
> Improve ldap auth type adding SearchScope variable in config file
> -----------------------------------------------------------------
>
> Key: OPENMEETINGS-1033
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1033
> Project: Openmeetings
> Issue Type: Improvement
> Components: LDAP
> Affects Versions: 3.0.3
> Reporter: Roberto E.L.
> Assignee: Maxim Solodovnik
> Fix For: 3.0.3, 3.1.0
>
>
> If you use SEARCHANDBIND method in LDAP auth type, OM makes only a onelevel
> search because the search scope is hardcoded in LdapLoginManagement class
> (src/main/java/org/apache/openmeetings/ldap/LdapLoginManagement.java, line
> code 237).
> EntryCursor cursor = conn.search(baseDn, searchQ, SearchScope.ONELEVEL, "*");
> It would be a good idea to include a searchScope variable in om_ldap.cfg
> where you can define the scope of the search: OneLevel or SubTree.
> In my ldap server, the users are stored in different branches of the ldap
> tree, so onelevel search only will find the users stored just one level below
> the base to search.
> Best regards.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
