SSL write error error:14095412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
Originally Published: 2008-01-17
Article Number
Applies To
RKM C client returns error 4780040, Bad Certificate
Issue
Resolution
This issue has also been seen when using IBM HTTP Server as the webserver, and the issuer of the client certificate was not trusted by IBM HTTP Server.
Follow iKeyMan procedures to import the client certificate's issuer in the Trusted CA store of your key database.
This can happen also if the webserver's Root CA certificate has expired or is not yet valid. Make sure all certificates in the chain are valid
Related Articles
Creating an alert view Number of Views How to resize the Oracle database alert.log for RSA Identity Governance & Lifecycle Number of Views Database ID Mismatch being reported in the alert log for RSA Identity Governance & Lifecycle Number of Views Unrecognized characters in syslog payload not allowing alerts to be processed in RSA Security Operations Management Number of Views Connecting to database gives error: "sslv3 alert handshake failure" Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
