I recently posted about updating our custom principal to store more information like user name and email which resulted in me having to move my code to the Application_PostAuthenticateRequest section (because we are using the Role Manager). Now that I have done that I realized my logic used to store and reload the custom information also needs to be updated.
The problem is that all the information I find on the topic is for Forms authentication. It appears that the FormsAuthenticationTicket is used to store the custom information in a cookie and restore after the initial load.
Is there something similar for Windows authentication using the Role manager with a custom principal?
...
Go to the complete details ...