This has been touched on earlier but no solutions have worked with my problem. My web app context is reverting back to generic principle whenever I change pages. Therefore the site principle is having to intialize everytime a page loads which sort of defeats the purpose of it.

My web config file is set to forms authentication. I can see no reason why it should loose its context everytime.

cheers Joe

I have the same exact problem. But what is strange is that it used to work before. It doesn't after I reinstalled my system. Can it be because of the version 1.1?

Anyway, I researched the web and it looks like the solving might be that instead of using Context.User = newPrincipal, you can use:

Thread.CurrentPrincipal = newPrincipal

I didn't try this, but I will when I get home...

Please let me know if you find any other solution too...

Iulian

hi,

I have tried using the thread.currentPrinciple but still am having no luck. it is still reverting back to the generic principle every time a page loads. DId you have any luck in sorting the problem out ??

joe

The only way I found is this:
instead of doing Context.User = myPrincipal, I do this:

Context["userid" + myPrincipal.Username] = myPrincipal;

Basically I cache the principal using the username as key. Then, in Global.asax in the OnRequestAuthenticate I do:

if (Request.IsAuthenticated)
{
 if (Context["userid" + Context.User.Identity.Name] != null)

or something like that. Basically, in the global.asax I restore the principal from the cached object and there you can set the principal and you won't loose it.

I also make sure I remove the key from the cache on Session end and everytime the user logs out...