Different User Context returned in high volume application

From: ts96gt (ts96gt_at_discussions.microsoft.com)
Date: 09/21/04


Date: Tue, 21 Sep 2004 06:59:05 -0700

I have an asp.net application that uses windows integrated authentication to
grant access to the site. When the default page loads, I grab the nt login
from the User.Identity.Name property, look relevant information up in the
database and return it to the screen.

This all works fine, until I get about 3 or four people to launch the site
simultaneously and repeatedly (to stress the app). When this happens, users
sometimes (not all times) get a different persons information. I narrowed
the issue down by creating a simple aspx page that just response.writes
User.Identity.Name. When we perform the same test, the same result occurs:
different user context's are returned.

A login prompt is not an option for this application, that is why I am
pulling information through this method.

Security setup:
 * permissions granted to folder where app resides to nt global group of
which all necessary users are a member of. I tried the app with
impersontation on and off to no avail.

Has anyone seen this issue before? Please provide any assistance that you
can. I have been dealing with this issue for a couple of weeks now. Thanks.

-- 
---


Relevant Pages

  • Authentication Sharing Across Apps
    ... For my part "B" question that I had (Login App was not returning ... authentication to calling app), I found the solution. ... Basically, in both the Login App and Calling App Web.Config, I did ... authenticated connection with SQL server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: QuickLaunch disappears
    ... I checked the login registery and I am pointing to the corrrect .exe. ... started and App, it crashed and sent a dump to Microsoft (this ... Documents and Settings I see "Lori Csontos" along with a "Lori". ...
    (microsoft.public.windowsxp.general)
  • Re: Session object timout
    ... > specifying your OS and IIS level, but the phenomenon may be caused by the ... > app is running in. ... >> users must go through a login page. ... >> recreating the session object which holds the class I mentioned above. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Permit only one network logon per user
    ... You app is controlling its listener and allowing/disallowing the ... allow a second connection to it using the same creds. ... multiple simultaneous logons with the same username and password ... If user username try to login from a different machine, ...
    (microsoft.public.windows.server.security)
  • Re: Session object timout
    ... Aside from the fact that I kind of like an application timing out for security ... setting of the Application Pool that your ASP.NET app is running in. ... Application pool was introduced in Windows 2003 with IIS 6.0, ... > users must go through a login page. ...
    (microsoft.public.dotnet.framework.aspnet)