Root (Server) and Client Certificates are RFC-5280 compliant starting in version 7.2.0 of RSA Identity Governance & Lifecycle
Originally Published: 2020-08-14
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.2.x
Issue
An example of a non RFC-compliant certificate (SKI > 20 octets) is shown below. Most octets are redacted but that is what the redaction is covering:
Resolution
Note: This only needs to be done if you have Remote AFX Agents and/or Remote Collection Agents. If certificates are not regenerated, the firewall issue mentioned above will continue to occur and multiple Remote AFX Server failures may also occur. See related RSA Knowledge Base Article 000039237 -- Multiple Remote AFX Server Failures caused by 'Issuer key identifier for the subject and the Subject key identifier for the issuer must be the same' after upgrading to version 7.2.0 of RSA Identity Governance & Lifecycle for more information.
An example of an RFC-compliant certificate (SKI restricted to 20 octets) is shown below. Although redacted, you can see the difference between this Subject Key Identifier and the one above.Notes
Related Articles
Change How Often the RADIUS Server Updates RADIUS Client Information 58Number of Views Checking service status of iptables in RSA Authentication Manager 8.4 returns 'Active: active (exited)'. 150Number of Views ASR fails to generate and the log file has 'ORA-04063: package body "AVUSER.SRSECTION_SYSTEM" has errors' errors in RSA Id… 216Number of Views RSA Announces the End of Support for RSA SecurID Authenticate for Windows 10 on Windows 10 Mobile 32Number of Views Trying to get a MSI package built to deploy SA SFTP Agent via SCCM. 37Number of Views
Trending Articles
Don't see what you're looking for?