Debug LDAP issue, not able to login with ConfigUI set to LDAP based.
Article ID: KB0093402
Updated On:
| Products | Versions |
|---|---|
| TIBCO API Exchange | - |
| Not Applicable | - |
Description
Description:
Steps to enable debug for ConfigUI.
Resolution
After following the documentation and the ConfigUI is changed to LDAP instead of FILE in both the TRA and server.xml file you are still unable to login, follow these steps to obtain more debug output:
Create a file called as ConfigUI_log4j.properties
--------------------------------------------------------------------------------------------------------------------------------------------------------
log4j.logger.com.tibco.amx.ra.authldap=DEBUG, Console, fa
log4j.logger.com.tibco.governance=DEBUG, fa
log4j.logger.com.tibco.amx.governance=DEBUG, fa
log4j.logger.com.tibco.asg.per=DEBUG,fa
log4j.logger.com.tibco.trinity=DEBUG,fa
log4j.logger.com.tibco.amx.ra=DEBUG,fa
log4j.logger.com.tibco.amx.governance.pa.action.authentication.AuthenticationAbstractAction=TRACE,fa
log4j.appender.fa=org.apache.log4j.FileAppender
log4j.appender.fa.File=debug.log
log4j.appender.fa.layout=org.apache.log4j.PatternLayout
log4j.appender.fa.layout.ConversionPattern=%d{yyyy MMM dd HH:mm:ss:SSS} %-5p [%t]: %m%n
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Add "-Dlog4j.configuration=file:///<path to above file>" to the java.extended.properties in the asg-configui.tra file. It is suggested to keep the log4j file in /bin so that there are no file permission issues. The -Dlog4j.Configuration property can be the file name as both the TRA and log4j file are in the /bin directory. Restart ConfigUI and you will find the debug.log file created.
Create a file called as ConfigUI_log4j.properties
--------------------------------------------------------------------------------------------------------------------------------------------------------
log4j.logger.com.tibco.amx.ra.authldap=DEBUG, Console, fa
log4j.logger.com.tibco.governance=DEBUG, fa
log4j.logger.com.tibco.amx.governance=DEBUG, fa
log4j.logger.com.tibco.asg.per=DEBUG,fa
log4j.logger.com.tibco.trinity=DEBUG,fa
log4j.logger.com.tibco.amx.ra=DEBUG,fa
log4j.logger.com.tibco.amx.governance.pa.action.authentication.AuthenticationAbstractAction=TRACE,fa
log4j.appender.fa=org.apache.log4j.FileAppender
log4j.appender.fa.File=debug.log
log4j.appender.fa.layout=org.apache.log4j.PatternLayout
log4j.appender.fa.layout.ConversionPattern=%d{yyyy MMM dd HH:mm:ss:SSS} %-5p [%t]: %m%n
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Add "-Dlog4j.configuration=file:///<path to above file>" to the java.extended.properties in the asg-configui.tra file. It is suggested to keep the log4j file in /bin so that there are no file permission issues. The -Dlog4j.Configuration property can be the file name as both the TRA and log4j file are in the /bin directory. Restart ConfigUI and you will find the debug.log file created.
Issue/Introduction
Debug LDAP issue, not able to login with ConfigUI set to LDAP based.
Feedback
Yes
No
Powered by
