- You publish an Outlook Web Access (OWA) website by using Microsoft Internet Security and Acceleration (ISA) Server 2006 Service Pack 1 (SP1) that uses RSA authentication.
- You authenticate client connections by using OWA Forms Based Authentication (FBA).
- You enable an idle time-out setting for Public Computers and set a specific time.
- You enable the No delegation, and client cannot authenticate directly or No delegation, but client may authenticate directly delegation setting.
- You connect to the OWA website from a public computer.
Note The correct behavior is to receive the reauthentication prompt when you resume to use OWA after you remained idle for the specified time.
When a public computer connects to the OWA website, they are prompted for credentials. However, the session times out after the time that is specified in the idle time-out configuration. Therefore, a new authentication is required while the connection remains active.
The script in hotfix 941162 reverses the behavior of ISA to be the same as before the hotfix and to have some UI exceptions. Additionally, you can specify a time-out for Private Computers by using the ISA Server Management console. You can still specify whether the client computer is a public computer or a private computer by using the options on the RSA SecurID form. However, these settings have no effect for Private Computers. If you reverse the effects of the script, and if you select the option that collects additional credentials, ISA uses the Private Computers time-out.
Article ID: 2481980 - Last Review: Dec 24, 2010 - Revision: 1