I could be totally wrong on this, but we had similar problems after
switching from Fasdtbind to BindLdap.
There was conflict between ldap jar files. The solution proposed had to do
with dependencies
We removed these files and error went away from the lib directory and the
problem went away.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am trying to get BindLdap working so I can look the Ldap password
policy enforcement module, and am running into a snag.
I followed the documentation here to make the changes:
http://www.ja-sig.org/wiki/display/CASUM/LDAP
When I go to log in, I
Any suggestions on what logging to increase or where to start digging?
Turn the ldap logger to DEBUG in the log4j.properties file:
log4j.logger.org.jasig.cas.adaptors.ldap=DEBUG
If that doesn't provide anything helpful, put org.jasig.cas in DEBUG
and try again.
M
--
You are currently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i already have this block in my logger:
log4j.logger.org.jasig.cas.adaptors.ldap.LdapPasswordWarningCheck=DEBUG
log4j.logger.org.jasig.cas.adaptors.ldap=DEBUG
log4j.logger.org.jasig.cas.ticket=DEBUG
log4j.logger.org.jasig.cas=DEBUG
I know it is
log4j.logger.org.jasig.cas.adaptors.ldap.LdapPasswordWarningCheck=DEBUG
log4j.logger.org.jasig.cas.adaptors.ldap=DEBUG
log4j.logger.org.jasig.cas.ticket=DEBUG
log4j.logger.org.jasig.cas=DEBUG
With those loggers you should see lots of output in the cas.log file
on authentication. If not,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am seeing lots of output -- just no errors when I get that to show on
the webpage.
Marvin Addison wrote:
log4j.logger.org.jasig.cas.adaptors.ldap.LdapPasswordWarningCheck=DEBUG
log4j.logger.org.jasig.cas.adaptors.ldap=DEBUG
