RSA Authenticator Utility does not import digital certificate which has an expiration date of 2/3/2106
Originally Published: 2006-01-09
Article Number
Applies To
Microsoft Windows XP Professional SP2
RSA SecurID SID800 Authenticator
RSA BSAFE Cert-C
Issue
Cause
Many of the standards implemented by Cert-C specify that GeneralizedTime can be used, which allows for dates beyond those that are able to be stored in a UINT4. Thus, Cert-C suffers from the Year 2106 problem by design.
Another issue is that, when ASN.1 parsing certificates, Cert-C currently does not allow full use of the possible date and time range. There is a Year 2099 limit hard-coded.
Resolution
Related Articles
Programatically create a user with no expiration date in RSA Authentication Manager 8.x Number of Views LDAP sync job cannot delete RSA ACE/Server user marked for deletion Number of Views AD account collector is not collecting the Last Login Date and Expiration Date in RSA Identity Governance and Lifecycle 7.0.2 Number of Views How can account access be prevented when a password expires based on the Password Expiration Date in a Password Policy def… Number of Views Disable the display of user information thumbnail when the screen is locked in RSA Authentication Agent 7.x for Windows Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…
Don't see what you're looking for?
