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 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 SECOND REMINDER: RSA Authenticator 4.3 for iOS and Android Coming Soon with New Look and More Number of Views
Trending Articles
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 How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update
Don't see what you're looking for?
