The Tomcat CSI realm plugs in to a Tomcat Web application container. Its purpose is to delegate authentication and authorization checks to the security provider.
To enable debugging in the Tomcat CSI realm
Open the logging.properties file located in $CATALINA_HOME/server/classes, where $CATALINA_HOME represents the Tomcat root installation directory, and add the property:
com.sybase.security.level = FINE
You can set the security level to any of these: OFF, SEVERE, WARNING, CONFIG, INFO, FINE, FINER, FINEST, or ALL.
The debugging output is written to the file whose name and location are specified by the logging.properties.appender.SecurityAppender.File property; in the example above, /opt/sybase/UA80/tomcat/logs/security_debug.log.
Create a log4j.properties file in $SYBASE/.../tomcat/common/classes to turn on debug tracing of CSI. The following gets you "DEBUG" and higher level tracing on the tomcat console:
#Tomcat server Logging Configuration
log4j.appender.RootAppender=org.apache.log4j.ConsoleAppender
log4j.appender.RootAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.RootAppender.layout.ConversionPattern=%d{ISO8601} %-5p %-25c{1} %x - %m%n
log4j.rootCategory=WARN, RootAppender
log4j.category.com.sybase.security=DEBUG
Initially, the Tomcat CSI realm is configured to use the PortalDB provider. To use the LDAP provider, see “Configuring the LDAP provider”.
