Shiro doesn't rely on any persistence strategy to be available and any APIs are read-only, so no, Shiro doesn't keep track of these details automatically. How you are doing it is ok - if you want a more reusable and better capsulated approach, consider implementing a custom realm and updating the last accessed record there.
Kalle On Wed, Sep 9, 2009 at 8:41 PM, Tauren Mills<[email protected]> wrote: > Currently, whenever a user logs into my system, the method > SecurityUtiles.getSubject().login(context) is run, followed by a > hibernate call that updates the user object with a new "last accessed" > date. > > I'm not having a problem with this, but I was just wondering if Shiro > is already keeping track of details like this and if there is a better > approach. > > Thanks, > Tauren >
