Java client looks for a new key when requested stale key is in the cache
Originally Published: 2008-02-08
Article Number
Applies To
Issue
Notes
The client contacts the server merely to maintain the integrity of the cache, as directed by the TTL value in the config file. The 2.1 server also returns key status/attributes so the client can determine if a key has been marked as compromised etc. (You would also need the 2.1 client R_KM_KEY_get_by_xxxx API to extract that information.), so this behavior is a lot more useful in 2.1.
Related Articles
RSA Authenticator 4.3 for iOS and Android Coming in August 2023 with New Look and More 32Number of Views In RSA Identity Governance & Lifecycle, when a user looks at a role in a role review that is on hold and presses OK instea… 19Number of Views A user sees an empty screen when looking at review items in RSA Identity Governance & Lifecycle 18Number of Views SA Looking for Live Manager Thick client in order to down load packages for off external Network SA Servers 5Number of Views When resetting an out of band (OOB) account password, Access Fulfillment Express (AFX) will always look for full DN to sea… 171Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?