Hello, Jerry,
You are right we should keep the topic, but I think this question came because I recommended to activate log4j to get the information what is happening around the LDAP authentication...
Log4J can be for the tracing of LDAP requests activated through following steps:
1. (Maybe not necessary, but for to be sure) Go to {TOMCATDIR}/webapps/ROOT/WEB-INF/classes/log4j.properties
and change it so it will produce the logging with debug, so for example like follows:
log4j.rootCategory=DEBUG, CONSOLE, MM1
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}:%L] %m%n
log4j.appender.MM1=org.apache.log4j.FileAppender
log4j.appender.MM1.File=c:/liferay.log
log4j.appender.MM1.Append=false
log4j.appender.MM1.layout=org.apache.log4j.PatternLayout
log4j.appender.MM1.layout.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}:%L] %m%n
(see also
http://logging.apache.org/log4j/ for additional log4j information)
2. Restart the portal and go in the first portal instance (if You created more of them, if not it is just the default) and here in the control panel to the section "server administration" and select there the tab "log levels". Search for the categories
com.liferay.portal.security.auth.LDAPAuth
com.liferay.portal.security.ldap
com.liferay.portal.security.ldap.PortalLDAPUtil
(in my case itwas on the 3rd page) and set the log level to "DEBUG"
(see the picture below)
3. Do not forget to save Your changes after the change by pressing the save button below.
So will be the log level of the given categories set to DEBUG. If You restart the portal, please verify the settings have not disappeared, we had sometimes this issue...
Now You should be able to track Your LDAP requests to see what is happening really in Your communication.
Bitte melden Sie sich an, um diesen Inhalt als unangebracht zu kennzeichnen.