[
https://issues.apache.org/jira/browse/OPENMEETINGS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175261#comment-14175261
]
David Benjamin commented on OPENMEETINGS-1105:
----------------------------------------------
Here is the only documentation I could find for phpLDAPadmin:
http://phpldapadmin.sourceforge.net/wiki/index.php/Config.php in the deref
section.
Here is a FAQ about aliases in OpenLDAP:
http://www.openldap.org/faq/data/cache/1111.html
And one more with a little more information:
http://www.zytrax.com/books/ldap/ch7/referrals.html#aliases
We are using Novell's eDirectory and have users that work at two different
schools which equals two different contexts. Our users are entered into one
schools context and an alias is created in the other schools context. When one
of those users tries to login using LDAP the eDirectory server returns two
objects and the login fails. From my reading I think we need to use
deref_never or dref_search.
Thanks,
David.
> Dereferencing Aliases using LDAP and eDirectory.
> ------------------------------------------------
>
> Key: OPENMEETINGS-1105
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1105
> Project: Openmeetings
> Issue Type: Bug
> Components: LDAP
> Affects Versions: 3.0.3
> Environment: java version "1.8.0_20"
> Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
> Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
> openSUSE 13.1
> eDirectory 8.8
> Reporter: David Benjamin
> Labels: ldap
>
> Users with aliases cannot login to Openmeetings.
> Java documentation:
> http://docs.oracle.com/javase/jndi/tutorial/ldap/misc/aliases.html
> Please add a configuration option in the
> webapps/openmeetings/conf/om_ldap.cfg file for how Java handles the
> dereferencing, maybe ldap_search_dereference. With the options always,
> never, finding or searching.
> I found the source code in this file: LdapLoginManagement.java
> I'm sorry I'm not a Java programmer but I can test and report back.
> David.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
