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 SECOND REMINDER: RSA Authenticator 4.3 for iOS and Android Coming Soon with New Look and More Number of Views A user sees an empty screen when looking at review items in RSA Identity Governance & Lifecycle 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 REMINDER: RSA Authenticator 4.3 for iOS and Android Coming in August 2023 with New Look and More Number of Views
Trending Articles
This certificate or its signing CA is not valid error when importing a certificate chain in RSA Authentication Manager 8.x… RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU How to create and configure certificates for HTTPS access when using intermediate CA certs in RSA Identity Governance & Li… RSA Authentication Manager Patch Updates
Don't see what you're looking for?
