Re: IIS user credentials caching
From: Russ (Russ.Cooper_at_RC.ON.CA)
Date: Tue, 16 Dec 2003 09:15:45 -0500 To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
From: "Peter Chang"
Date: Sat, 29 Nov 2003 07:10:03 -0800
This has pretty much always been the case (to improve performance) and is a problem which often comes up in a production environment at some point or other when trying to make a change for a user on the fly. The IIS user token is cached for 15 minutes. Q152526 describes how to change this default timeout. Keep in mind that caching is done to improve performance. The key is to find the right balance for your environment.
From: "Tesch, Robert C"
Date: Mon, 1 Dec 2003 09:18:02 -0600
So yes what you are seeing is "by design". Also from the "for what it's worth department" I would not try to shorten that session time, especially if this server is "behind" the firewall and used internally. We have kept ours at 20 minutes and the users are continually bi+c^!ng that the sessions are timing out too quickly.
Russ - NTBugtraq Editor
Want to reply to the person who sent this message?
This list is configured such that just hitting reply is going to result in the message coming to the list, not to the individual who sent the message. This was done to help reduce the number of Out of Office messages posters received. So if you want to send a reply just to the poster, you''ll have to copy their email address out of the message and place it in your TO: field.