Home > Default > SSLHandShakeException's fatal alert certificate_unknown

SSLHandShakeException's fatal alert certificate_unknown

October 11Hits:8
Advertisement
Trying to connect RMI SSL Client with RMI non-SSL Server with and getting following exception. How should i check SSLHandShakeException's fatal alert certificate_unknown in the code ? Also I am setting SSL properties(keystore, truststore, passwords) using System.setPropertiy()
*** ServerHelloDone
RMI TCP Connection(11)-10.229.194.39, WRITE: TLSv1 Handshake, length = 659
RMI TCP Connection(11)-10.229.194.39, READ: TLSv1 Alert, length = 2
RMI TCP Connection(11)-10.229.194.39, RECV TLSv1 ALERT: fatal, certificate_unknown
RMI TCP Connection(11)-10.229.194.39, called closeSocket()
RMI TCP Connection(11)-10.229.194.39, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
RMI TCP Connection(11)-10.229.194.39, called close()
RMI TCP Connection(11)-10.229.194.39, called closeInternal(true)
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
RMI TCP Connection(12)-10.229.194.39, setSoTimeout(7200000) called
RMI TCP Connection(12)-10.229.194.39, READ: SSL v2, contentType = Handshake, translated length = 73
*** ClientHello, TLSv1
RandomCookie: GMT: 1360739234 bytes = { 103, 192, 214, 126, 21, 70, 8, 98, 28, 38, 177, 79, 93, 98, 219, 3, 14, 199, 232, 12, 186, 102, 148, 116, 240, 107, 25, 14 }
Session ID: {}

Answers

890918 wrote:
Trying to connect RMI SSL Client with RMI non-SSL Server with and getting following exception.What you have posted is not an exception, it is an SSL debug trace, and you could not possibly have got it by connecting to a non-SSL server.

Read other 4 answers

Tags:

Related Articles

  • SSLHandShakeException's fatal alert certificate_unknownOctober 11

    Trying to connect RMI SSL Client with RMI non-SSL Server with and getting following exception. How should i check SSLHandShakeException's fatal alert certificate_unknown in the code ? Also I am setting SSL properties(keystore, truststore, passwords)

  • SSL: Received fatal alert: certificate_unknown ProblemOctober 11

    Hi all, first I read this thread http://forums.sun.com/thread.jspa?threadID=5385002 but I didnt help me so i startad a new one. I´m doing a client, server and thread implementation with ssl, i copied certifcates and keystores on the directories and s

  • Received fatal alert: certificate_unknownOctober 11

    i am making a SSL client server application. i got this exception javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown         at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)         at com.sun.net.ss

  • Https Issue:SSLHandshakeException:Received fatal alert:bad_certificateOctober 11

    hi experts,   My scenario is Proxy to AS2. In AS2 receiver I have https protocol. I have put SSL Certificate(keystore) value. Let say View-  x Certificate name-  cer then I  have given TRUSTED\x\cer in SSL Certificate(keystore) field of AS2 receiver

  • SSLHandshakeException: Received fatal alert :handshake_failureOctober 11

    Hola forum, I'm having a bit of a problem with ssl sockets currently. Please bear with me as this is my first run at using ssl sockets for anything and I've done a fair bit of searching on google already. Here's the code I'm using: (kindly ignore any

  • Received fatal alert: handshake_failure!!October 11

    Hi all, I have to connect with a server via mutual authentication. I have to received a server certificate and send my client certificate, which I have stored in cacerts. This certificate is a class 3 certificate from verisign. If I try to connect fr

  • Why get "fatal alert: bad_certificate" but "certificate_expired"October 11

    Hi all, I am testing 2 way SSL authentication now. Expected Result: When the client side provides a expired client cert to the server during handshaking, the server is supposed to return fatal alert: certificate_expired, which is exactly the client s

  • Client Auth failure:SSLException Received fatal alert: bad_certificateOctober 11

    Friends, I have managed to establish a one -way https connection between the client and the tomcat-server by keeping the client-Authentication=false <Connector enableLookups="true" port="8443" scheme="https" secure="t

  • Client Authentication - Received fatal alert: bad_certificateOctober 11

    I am making a "secure" chat server that has some simple functionality. For the server cert, I sent off the CSR to Thawte and set up the trust chain. That keystore seems to be fine: Keystore type: jks Keystore provider: SUN Your keystore contains

  • CA-Signed certificate: Received fatal alert: bad_certificateOctober 11

    Hello. I am still trying to get rmi ssl to work in the way I want (see my post http://forums.sun.com/thread.jspa?threadID=5351278&tstart=15 ). I read that CA signed certificates are preferred to self signed certificates due to several reasons. Due to

Copyright (C) 2019 wisumpire.com, All Rights Reserved. webmaster#wisumpire.com 14 q. 0.599 s.