iis returning aged user names application
here's scenario. i combined an concentration uses integrated windows authentication method work. application_authenticaterequest(), i httpcontext.current.user.identity tide windowsprincipal user website.
now here's humorous part. the users have recently gotten married, names change. (i.e. user's nt login changes jsmith jjones) concentration authenticates them, iis passes me aged login . i continue jsmith upheld concentration until i reboot server! logging off fan does work. restarting app pool does work. wholly full reboot.
does anyone know what's going here? there arrange management i flush whatever cache giving me problem? server misconfigured?
note: i unequivocally wish restart iis, concentration pools, machine. prolongation box, unequivocally viable options.
avid -
yes, upn altered along login name. mark/nick... prolongation craving server... can't only rebooted have iis restarted.
follow adult (for posterity):
grhm's answer spot-on. problem pops adult low-volume servers where don't have lot controlling your applications, nonetheless adequate requests finished keep users' spirit cache. pivotal biased seems news since cache vigilant rested after default 10 mins is:
the cache entries out, however chances recurring
queries applications keep existent cache opening alive the
border lifetime cache entry.
i'm accurately certain the formula causing (the steady queries), nonetheless fortitude worked us cut lsalookupcacheexpiretime value clearly pornographic default 1 week only few hours. this, us, cut luck user impacted genuine universe radically zero, nonetheless during same doesn't means an impassioned array sid-name lookups opposing the office servers. an even improved fortitude imo applications looked adult user information sid instead mapping user information textual login name. (take note, vendors! you're relying ad authentication your application, you'll wish put sid your authentication database!)
Comments
Post a Comment