Java client looks for a new key when requested stale key is in the cache
Originally Published: 2008-02-08
Last Modified: 2023-09-25
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 Number 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… Number of Views A user sees an empty screen when looking at review items in RSA Identity Governance & Lifecycle Number of Views SA Looking for Live Manager Thick client in order to down load packages for off external Network SA Servers Number of Views Look up a User ID and/or associated Logon Aliases in Authentication Manager 8.x (at the command line) Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn… RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console
Don't see what you're looking for?
