Well, I think there was a misunderstanding in my group of how to use mmUserManager in a Web application. In our DataAccess classes we have rules that create history in the Database when data has changed. Those rule require a way to get the id of the user currently logged into that session, so that the id can be included in the history records saved in the database. But it doesn't appear that the user's id is cached or stored in the session automatically by any of the Mere Mortals architecture.

What I wanted to find out is if there is going to be some mechanism in the next version of Mere Mortals that will cache the user's id once logged in, so it can then be accessed throughout the system without necessarily having to re-authenticate the user. Or do I need to build this behavior myself?