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 Number of Views Change the Character Length for On-Demand Authentication Tokencodes Number of Views How to use Link Gopher to determine additional proxy web servers to set up for a SecurID Access HFED Application Number of Views How to setup On-Demand Authentication (ODA) in RSA Authentication Manager 8.x Number of Views Recognize - SecurID Access Implementation Guide Number of Views
Trending Articles
Report preview and/or generation fails with 'java.lang.NoClassDefFoundError: Could not initialize class net.sf.jasperrepor… How to set up the REST RSA SecurID Authentication API for Authentication Manager 8.2 SP1 RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Change the Token Lifetime Extension Window in Authentication Manager Using rsautil
Don't see what you're looking for?
