How to set cookie expiration times
Originally Published: 2000-09-25
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
Programatically create a user with no expiration date in RSA Authentication Manager 8.x Number of Views Inviting a user using HDAP throw an error: " Invite User Operation Failed " Number of Views RSA Governance & Lifecycle Recipes: System Health Check Dashboard Number of Views Token Expiration Report takes long time to return and eventually failed - RSA Authentication Manager 8.1 Number of Views Upgrading RSA Identity Governance & Lifecycle 6.9.1 to 7.0.0 fails due to an NTP Service Connectivity issue Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
