> and in my ldap log I can see : > > Jan 18 14:53:27 debian slapd[4380]: conn=0 fd=14 ACCEPT from > IP=127.0.0.1:37509 (IP=0.0.0.0:389) > Jan 18 14:53:27 debian slapd[4380]: conn=0 op=0 BIND > dn="cn=admin,dc=exemple,dc=com" method=128 > Jan 18 14:53:27 debian slapd[4380]: conn=0 op=0 BIND > dn="cn=admin,dc=exemple,dc=com" mech=SIMPLE ssf=0 > Jan 18 14:53:27 debian slapd[4380]: conn=0 op=0 RESULT tag=97 err=0 text= > Jan 18 14:53:27 debian slapd[4380]: conn=0 op=1 SRCH > base="dc=exemple,dc=com" scope=2 deref=3 > filter="(cn=homer,dc=exemple,dc=com)" > Jan 18 14:53:27 debian slapd[4380]: conn=0 op=1 SRCH attr=1.1 > Jan 18 14:53:27 debian slapd[4380]: <= bdb_equality_candidates: (cn) not > indexed > Jan 18 14:53:27 debian slapd[4380]: conn=0 op=1 SEARCH RESULT tag=101 > err=0 nentries=0 text=
That looks like a successful admin bind and search. I don't see the subsequent user bind that would be needed for a successful authentication in CAS. Can you please turn up the verbosity of the CAS log by editing the $CATALINA_HOME/webapps/cas/WEB-INF/classes/log4j.properties file? Put the org.jasig.cas.adaptors.ldap package in DEBUG and see if that provides more information. If that doesn't produce anything helpful, you can try putting the org.jasig.cas package in DEBUG. Note that this will produce cleartext passwords in the cas.log file. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
