11-09-2010 12:46 PM
# ldapsearch -x -v -b <searchbase> -D <dn_of_a_privileged_user> -H ldaps://<server>:636 -W <query>
11-11-2010 08:04 AM
…
searching the user DN and then authenticate using this DN.
….
This was fixed in v3.2r.
If you set ldap.authentication.userNameFormat to be empty (now the default for the ldap subsystem)
ldap.authentication.userNameFormat=
it will derive a query from your personQuery to look up a user by UID. So we can now support users in any structure you want.
ldap.authentication.active=true
ldap.authentication.allowGuestLogin=false
ldap.authentication.userNameFormat=
ldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
ldap.authentication.java.naming.provider.url=ldaps://<my_ldap_server>:636
ldap.authentication.java.naming.security.authentication=simple
ldap.authentication.escapeCommasInBind=false
ldap.authentication.escapeCommasInUid=false
ldap.synchronization.active=false
ldap.synchronization.java.naming.security.principal=cn\=search_privileged_user,ou\=example_ou,dc\=example,dc\=com
ldap.synchronization.java.naming.security.credentials=secret
ldap.synchronization.userSearchBase=ou\=example_ou,dc\=example,dc\=com
ldap.synchronization.userIdAttributeName=example_uid
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.