Last post May 24, 2011 02:26 AM by jimmy q
Jul 20, 2010 11:08 AM|furious_vibes|LINK
I have an ASP.Net application using Integrated Security. A week ago, one of my users got married and changed her name. Thus IT updated AD and her domain UserID also changed.
Since this happened, whenever IIS authenticates her identity, it recognizes her as her old userID (not the new one, which she now uses to log into Windows).
At first, I figured her computer must be caching some credential information and passing out of date info to IIS, so I got her to try logging in from another computer: this still returned the old userID.
I found only one other forum post on this subject:
but so far have found it unhelpful. I changed the server's local security policy to dissalow .net credential storage and restarted the server. The user was able to log in after the restart, but it turns out that it was because of the restart of IIS (I confirmed
this by recreating the issue with a test account and seeing the problem persists).
I am at my wit's end, and need to find a solution, since restarting IIS is not a practical remedy and this is bound to happen again in the future.
May 24, 2011 02:26 AM|jimmy q|LINK
Not sure but how about just recycling the application pool?