audit configuration and use
jGuard has got an audit feature since release 0.70:
all decisions taken by jGuard after evaluating if you are authorized to access to the desired resource are notified to the AuditManager class of package net.sf.jguard.audit.
these decisions or Events, are logged and contains a cause, and a consequence.
so, to see them, you have to configure the logging level and appender of the package net.sf.jguard.audit.
jGuard use the logging wrapper library commons-logging.so, if your underlying logging system is log4j, you have to
configure logs of this package like that:
log4j.logger.net.sf.jguard.audit= INFO,stdout,file
## Default logger; will log *everything*
log4j.rootLogger= INFO,file
log4j.logger.net.sf.jguard= INFO,file
log4j.logger.org.apache.struts = WARN,stdout
log4j.logger.net.sf.jguard.audit= INFO,stdout,file
log4j.additivity.net.sf.jguard= false
# stdout appender
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%r [%t] %-5p %c %x - %m%n %L
#file appender
log4j.appender.file=org.apache.log4j.FileAppender
log4j.appender.file.file=jguard.log
log4j.appender.file.layout=org.apache.log4j.PatternLayout
log4j.appender.file.layout.ConversionPattern=%r [%t] %-5p %c %x - %m%n
Version 1.6 last modified by Charles Gay on 28/09/2006 at 17:51
Comments: 0