In ISA Server 2006, you cannot set a session time-out for private computers in a Web listener that has the RSA SecurID authentication method configured

In Microsoft Internet Security and Acceleration (ISA) Server 2006, you cannot set a session time-out for private computers in a Web listener that has the RSA SecurID authentication method configured.

If the Collect additional delegation credentials in the form check box is not selected in Authentication tab of the Web listener properties, the Timeout for private computers box is disabled in the Advanced Form Options dialog box.

If the Collect additional delegation credentials in the form check box is selected in Authentication tab of the Web listener properties, the Timeout for private computers box is enabled in the Advanced Form Options dialog box. However, the RSA credentials always time out according to the value in the Timeout for public computers box, regardless of the value in the Timeout for private computers box.

By default, ISA Server 2006 does not support a time-out setting for private computers when RSA SecurID authentication is used.

To resolve this problem, apply the hotfix package that is described in the following Microsoft Knowledge Base article: Notes

• After you apply this hotfix, you can set a session time-out both for private computers and for public computers. The fix for this problem applies only when you use the default form that ISA Server provides.
• The hotfix replaces the Usr_pcode.htm file with an updated file version. The Usr_pcode.htm file resides in the following folder:
  <ISA_Install_Dir>\CookieAuthTemplates\ISA\HTML
  The <ISA_Install_Dir> placeholder represents the location where ISA Server 2006 is installed. If you have customized the Usr_pcode.htm file, the hotfix does not replace the file. Therefore, the RSA SecurID form does not display the options to specify whether the client computer is a public computer or a private computer. In this situation, you have to restore the original Usr_pcode.htm file, apply the hotfix, and then re-customize the Usr_pcode.htm file.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.