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
How to setup On-Demand Authentication (ODA) in RSA Authentication Manager 8.x Number of Views Which RSA Cloud Authentication Service tenant am I using? Number of Views Configure the RSA Authentication Agent API for Java on a supported platform with two network card interfaces (NIC) Number of Views How to set emergency access tokencode lifetime for permanently lost or broken RSA SecurID tokens Number of Views How to implement SAML SSO Authentication with Microsoft Azure Active Directory and RSA Identity Governance & Lifecycle Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
