Re: Security problem/issue ASP.Net
From: Kevin Spencer (kevin_at_DIESPAMMERSDIEtakempis.com)
Date: 02/07/05
- Next message: Kevin Spencer: "Re: Debugging Javascript file"
- Previous message: Saravana: "Re: Code called twice"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: Security problem/issue ASP.Net"
- Next in thread: Gilles: "Re: Security problem/issue ASP.Net"
- Reply: Gilles: "Re: Security problem/issue ASP.Net"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 7 Feb 2005 12:41:11 -0500
> The Web Server is set to:
> "Integrated Windows authentication"
> and "Anonymous access" is disabled.
> What else can I do to avoid this session mix ?
I'm not sure. I haven't had to deal with this issue before. But if I'm
reading the SDK correctly, you need to set the "identity impersonate"
attribute to true. From what I've read, this enables "per request"
impersonation.
-- HTH, Kevin Spencer Microsoft MVP .Net Developer Neither a follower nor a lender be. <anonymous@discussions.microsoft.com> wrote in message news:142e01c50d32$01c60e10$a501280a@phx.gbl... > Thanks for your quick reply, > > The Web Server is set to: > "Integrated Windows authentication" > and "Anonymous access" is disabled. > What else can I do to avoid this session mix ? > > Thanks > > Gilles >>-----Original Message----- >>HttpContext.Current.User.Identity represents the > currently logged-in user. >>If the web disallows anonymous authentication, this will > (probably) be a >>different user with each client. If anonymous browsing is > allowed, the user >>will always be the Anonymous Internet User account. >> >>-- >>HTH, >> >>Kevin Spencer >>Microsoft MVP >>..Net Developer >>Neither a follower nor a lender be. >> >>"Gilles" <anonymous@discussions.microsoft.com> wrote in > message >>news:24b601c50d2e$a23116f0$a401280a@phx.gbl... >>> Hello, >>> I'm facing a big problem in an Asp.Net application, when >>> users connect the application, I store their user >>> informations into the session object (session_start). >>> But when 2 users click (nearly) at the same time on the >>> page myprofile, the first user sees his profile (the >>> correct one) and the second sees the profile of the > first >>> (very bad). >>> the "HttpContext.Current.User.Identity" is not the >>> expected one. >>> web.config entries: >>> <authentication mode="Windows"/> >>> <identity impersonate="false"/> >>> <authorization> >>> <allow users="*"/> >>> </authorization> >>> <sessionState mode="InProc" cookieless="false" >>> timeout="20"/> >>> Any idea ? >>> Many thanks for your help. >>> Gilles >> >> >>. >>
- Next message: Kevin Spencer: "Re: Debugging Javascript file"
- Previous message: Saravana: "Re: Code called twice"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: Security problem/issue ASP.Net"
- Next in thread: Gilles: "Re: Security problem/issue ASP.Net"
- Reply: Gilles: "Re: Security problem/issue ASP.Net"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|