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
Inviting a user using HDAP throw an error: " Invite User Operation Failed " Number of Views Termination Date is not populated with the Account Expires date when running an Active Directory Identity Collector (IDC) … Number of Views Import a Digital Certificate Number of Views Authentication Agent for Windows v. 7.4.x Challenge lookup fails with "Cannot open challenge cache data key for user <User… Number of Views How to convert the date field number from a request form to a human readable date in RSA Via Lifecycle and Governance Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud Administration audit logs using Cloud Administration REST API CLU
Don't see what you're looking for?
