We need to set a few session variables at login time which is then cleared when the user logs out, is there a "best practice" way to do this? I mean, besides actually modifying the DNN Core? We have created our own membership provider to facilitate the usage of client certificates for logins, which could of course handle it, but since that is in the business layer it just doesn't feel right. We could of course also change the definition in the ModuleControls and make our own login.ascx/logoff.ascx but that would also mean that we need to take care when doing future upgrades, and isn't much more pretty than changing in the core itself.

Is there still no "hook" available in the login and logof procedures that can be used for customizing stuff with regards to login/logoff? I tried to search for this topic but doesn't really know what keywords to search for...someone must have done this before. The AuthenticationLogoffBase and AuthenticationLogonBase classes kind of gives the impression that the purpose could be something like we have been looking for, but I am not sure.



/pJ

at present there isn't documentation for these, it's been worked on AFAIK. The code is the best reference at present. I recommend you take a look at any of the alternative authentication providers such as the openid or liveid ones as they'll give you a good idea how to create your own provider. An alternative to this would be to hook up the necessary events via a httpmodule.

Cathal

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US