The Tomcat CSI realm plugs in to a Tomcat 4.1 Web application container. Its purpose is to delegate authentication and authorization checks to the security provider.
To enable debugging in the Tomcat CSI realm, create a file called log4j.properties in %CATALINA_HOME%\server\classes, where CATALINA_HOME represents the Tomcat root installation directory, and insert the following text:
# sample log4j.properties
# SecurityAppender for security packages only
log4j.appender.SecurityAppender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.SecurityAppender.DatePattern='.'yyyy-MM-dd
log4j.appender.SecurityAppender.File=D:/ep61unwire/infoedition/tomcat/logs/
security_debug.log
log4j.appender.SecurityAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.SecurityAppender.layout.ConversionPattern=%d{ISO8601}
%-5p %-25c{1} %x - %m%n
log4j.category.com.sybase.security=DEBUG, SecurityAppender
# make sure security messages stay in the security log
log4j.additivity.com.sybase.security=false
# other packages go to the root appender
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=INFO, RootAppender
The debugging output is written to the file whose name and location are specified by the log4j.appender.SecurityAppender.File property; in the example above, D:\ep61unwire\infoedition\tomcat\logs\security_debug.log.
Initially, the Tomcat CSI realm is configured to use the PortalDB provider. To use the LDAP provider, see “Configure the LDAP provider”.
| Copyright © 2004. Sybase Inc. All rights reserved. |
|
|
