Asp.Net: Storing Principal in httpcontext.current.items
Posted
by Pickels
on Stack Overflow
See other posts from Stack Overflow
or by Pickels
Published on 2010-05-06T12:47:30Z
Indexed on
2010/05/06
12:58 UTC
Read the original article
Hit count: 335
Hello,
I was wondering if there are any downsides of storing a custom Principal in httpcontext.current.items instead of the httpcontext.current.user. I know you need to set it for each request but I have to do that with httpcontext.current.user also.
thanks in advance,
Pickels
© Stack Overflow or respective owner