javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 843811, 1 year ago
FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
via Oracle Community by 666705, 1 year ago
FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
via Oracle Community by 3004, 1 year ago
FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
via Google Groups by Sheethal Shenoy, 5 months ago
FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
via Oracle Community by 666705, 1 year ago
FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
via Google Groups by Nenad, 5 months ago
FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(UnknownSource)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(UnknownSource)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(UnknownSource)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(UnknownSource)
at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
at com.certicom.tls.record.ReadHandler.interpretContent(UnknownSource)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(UnknownSource)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(UnknownSource)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.sun.jndi.ldap.Connection.(Connection.java:209)
at com.sun.jndi.ldap.LdapClient.(LdapClient.java:108)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2379)
at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:239)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:74)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.(InitialContext.java:193)
at javax.naming.directory.InitialDirContext.(InitialDirContext.java:78)
at jsp_servlet.__wl._jspService(__wl.java:129)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 2 years ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
5 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.