Re: RolePrincipal vs Custom Principal
- From: Dominick Baier <dbaier@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 17 Jan 2007 16:32:54 +0000 (UTC)
well - you end up with a RolePrincipal because RoleManager is enabled - just disable it and you don't have to "hack" your way trough...
<roleManager enabled="false" />
-----
Dominick Baier (http://www.leastprivilege.com)
Its ok found the answer in this group - use the postauthenticate
event!! works fine.
LetoLtd wrote:
I have a custom IPrincipal class that I setup and put into
Context.User in the Application_AuthenticateRequest, all works fine.
However when I check the HttpContext.Current.User in a page my Custom
IPrincipal has been overwritten by the RolePrincipal class, how do I
stop it doing this?
Thanks
.
- References:
- Re: RolePrincipal vs Custom Principal
- From: LetoLtd
- Re: RolePrincipal vs Custom Principal
- Prev by Date: Re: RolePrincipal vs Custom Principal
- Next by Date: RE: Better security
- Previous by thread: Re: RolePrincipal vs Custom Principal
- Next by thread: Re: ApplicationName: Create programmatically
- Index(es):