After successfull validation on my Login.aspx page I execute the following code:-

PayDayLoan.WebModules.Accounts.Business.PhilePrinc ipal newUser = PayDayLoan.WebModules.Accounts.Business.PhilePrinc ipal.ValidateLogin( SSN.Text.Trim(), Password.Text.Trim() );
Context.User = newUser;
FormsAuthentication.SetAuthCookie( SSN.Text, true );

In my Web.Config file I have following configuration :-

<authentication mode="Forms">
    <forms name="PayDayLoanWebsite" path="/"
      loginUrl="/PayDayLoanWebsite/Modules/Accounts/Login/Login.aspx"
      protection="All" timeout="30">
   </forms>
 </authentication>

But when I go to the next page, MyAccount.aspx, the Context.User.GetType() returns me "System.Security.Principal.GenericPrincipal" in my application where as in ThePhile it returns "Wrox.WebModules.Accounts.Business.PhilePrincipal" ; which is what I want, I think I should get "PayDayLoan.WebModules.Accounts.Business.PhilePrin cipal"; which I am not. Somehow I am loosing the context between the pages.

Please help me with this problem.

Thank you.

Niketu

Hello,

I'm having the same problem too, it's not carrying the object reference for some reason. If you don't find a solution, consider using the Cache or Session to maintain the object reference.

Brian

Brian,

I haven't seen this problem myself.

I agree that putting it in session state is a good idea, but I wouldn't put an individual user's security context in the cache because it's not fundamentally isolated. It's not good to depend on home-grown source code to keep the users separated (might work good, but seems like a security risk).

Did you see my posting here - is this how you set up your page:
http://p2p.wrox.com/topic.asp?TOPIC_ID=15318

I'm debating going to a simpler model based on Generic Principal instead of a custom Principal. Have you considered this? The Microsoft TimeTracker Starter Kit has a good, and simple, implementation of Generic Principal.

Eric