javax.naming.CommunicationException: simple bind failed
Vignesh, Vanna G.
vignesh at musc.edu
Tue Aug 25 18:07:29 EDT 2015
I am using AD for authentication. It works fine with ldap and 389. However, if I use ldaps with port 389/ ssl= true and tls=false, it is throwing error saying that cannot bind simple dn.
Is there any where I need to put the AD certificates? If yes, what format and how? Thanks.
Here is my config:
edu.vt.middleware.ldap.jaas.LdapLoginModule sufficient
ldapUrl="LDAPS://*********"
port="636"
ssl="true"
tls="false"
baseDn="*******"
subtreeSearch="true"
userFilter="sAMAccountName={0}"
bindDn="****"
bindCredential="***";
I also tried the following. It gave illegal argument error.
edu.vt.middleware.ldap.jaas.LdapLoginModule sufficient
ldapUrl="LDAPS://*********"
port="636"
ssl="true"
tls="false"
baseDn="*******"
subtreeSearch="true"
userFilter="sAMAccountName={0}"
sslSocketFactory="{trustCertificates=file:/opt/shibboleth-idp/credentials/****.p7b}"
bindDn="****"
bindCredential="***";
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150825/5fc788ba/attachment.html>
More information about the users
mailing list