audit configuration and use

Last modified by RaffaelloPelagalli on 2005/12/01 22:04

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, if your underlying logging system is log4j, you have to configure logs of this package like that: INFO,stdout,file

here is the complete example

## Default logger; will log *everything*
log4j.rootLogger= INFO,file INFO,file = WARN,stdout INFO,stdout,file false
# stdout appender
log4j.appender.stdout.layout.ConversionPattern=%r [%t] %-5p %c %x - %m%n %L
#file appender
log4j.appender.file.layout.ConversionPattern=%r [%t] %-5p %c %x - %m%n
Created by diabolo512 on 2005/12/01 21:48

jGuard team copyright 2004-2009