There are two ways that we track logins/logouts. We use inspektr and send audit logs to our central syslog server. You can also set this up to use JDBC.
Here is how we have this setup using logback: <appender name="SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender"> > <syslogHost>the_sysloghost</syslogHost> > <facility>user</facility> > </appender> > > <logger > name="com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager" > additivity="false" level="INFO"> > <appender-ref ref="SYSLOG" /> > </logger> We also get user login/logout details for our own troubleshooting by setting the following log levels: <logger name="org.jasig.cas.ticket" leve="INFO" /> > <logger name="org.jasig.cas.authentication" level="INFO" /> This is slf4j/logback, and CAS ships with log4j. You could route these to a separate FILE appender to separate them out from the other logs if you wish. -Adam On Wed, Mar 11, 2015 at 11:16 AM, Dmitriy Kopylenko <[email protected]> wrote: > There is a way to configure Inspektr library in CAS to persist its > captured audit events in RDBMS: > > https://wiki.jasig.org/display/CASUM/Auditing+and+Statistics+Via+Inspektr > > Not sure if there is a newer version of the above documentation resource, > though. > > Another way to capture and process significant CAS events is to use the > following facility (available as an addon module): > > https://github.com/Unicon/cas-addons/wiki/CAS-server-events > > This method might be attractive as it is de-coupled from most CAS > internals. Just need to wire it in and implement listeners receiving the > data of interest and do whatever is desired with that data. > > Here’s an example of such listener facility which listens for couple of > these events and records them as stats in Redis server: > > > https://github.com/Unicon/cas-addons/wiki/Record-statistics-for-CAS-events-in-Redis-server > > Best, > Dmitriy. > > On Mar 11, 2015, at 10:56 AM, Maxwell, Gary <[email protected]> > wrote: > > We were hoping to place the history in a db. The info would then be > accessed via web services. > > *From:* Christopher Myers [mailto:[email protected] > <[email protected]>] > *Sent:* Wednesday, March 11, 2015 8:43 AM > *To:* [email protected] > *Subject:* Re: [cas-user] CAS login history > > Is there a specific way that you need to be able to reference it? Our CAS > setup keeps information about it in Tomcat's catalina.out files, so we can > pull it from there. > > Chris > > >>> "Maxwell, Gary" <[email protected]> 03/11/15 9:35 AM >>> > > Is there a feature with CAS that will keep a history of Logins and Logouts? > > Thanks Gary > > -- > 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 > > -- > 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 > > -- 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
