This is done by the library called Inspektr and configured in CAS by annotating methods of the internal CAS server implementation that represent these key audit points with the special annotation provided by this library. Then these annotated audit points (methods) are advised by the Inspektr's AOP aspect which in turn delegates to pluggable AuditTrailHandlers. The default one is being a log one. The Inspektr's config resides in auditTrailContext.xml
https://github.com/dima767/inspektr/wiki/Inspektr-Auditing Cheers, Dmitriy. On Nov 30, 2011, at 6:28 PM, "Richard" <[email protected]> wrote: > In CAS, after you logged in, you got something like this in your log file: > > > INFO [com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - > <Audit trail record BEGIN > ============================================================= > WHO: [username: username] > WHAT: supplied credentials: [username: username] > ACTION: AUTHENTICATION_SUCCESS > APPLICATION: CAS > WHEN: Wed Nov 30 15:28:15 NZDT 2011 > CLIENT IP ADDRESS: client.ip > SERVER IP ADDRESS: server.ip > ============================================================= > > > I just want to know where this log information comes from? In other word, > where should I change if I want to change this log information? > > Thanks, > > Richard > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
