How to set cookie expiration times
Originally Published: 2000-09-25
Last Modified: 2023-10-06
Article Number
Applies To
RSA ACE/Agent 4.4 for Windows NT (no longer supported as of 3-3-2003)
Netscape Navigator browser does not experience this problem
Issue
A SecurID user accesses a protected page and gets challenged. If that user browses to another page and then hits BACK to the protected page, they are not challenged again.
To ensure that cookie timeouts are enforced, you need to enable the option in your browser to always force pages to update. Doing so ensures that the page is refreshed and cookie time validity is checked by our code. If the pages are not refreshed, the client code will not check the time validity on the cookies. Even if the cookie expiration time is in the past, the user will not be prompted for SecurID authentication.
Cause
Resolution
1. From the top menu, select on Tools --> Internet Options
2. Under the Advanced tab, select "Automatically check for Internet Explorer Updates"
Related Articles
On-Demand Authentication 15Number of Views How to setup On-Demand Authentication (ODA) in RSA Authentication Manager 8.x 1.3KNumber of Views On-Demand Authentication 61Number of Views Prove SMS Gateway - RSA Ready Implementation Guide 25Number of Views Select On-Demand Authentication for Provisioning 7Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?