2 Replies Latest reply on Nov 4, 2003 1:12 AM by dgb

    Problems with the authentication of the client in Jboss with

    dgb
    dgb Oct 24, 2003 5:06 AM

      Hi! I have a problem with the authentication. When I active the authentication (clientAuth="true") in the file jboss-service.xml and I start the server, the result is ever the same when I connect with https:

      2003-10-24 11:44:42,908 DEBUG [org.apache.tomcat.util.threads.ThreadPool] Getting new thread data
      2003-10-24 11:44:43,699 DEBUG [org.apache.tomcat.util.net.PoolTcpEndpoint] Handshake failed
      javax.net.ssl.SSLHandshakeException: null cert chain
      at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.a(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SunJSSE_aw.a(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SunJSSE_aw.a(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SunJSSE_ax.a(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA6275)
      at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocketFactory.java:290)
      at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:540)
      at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
      at java.lang.Thread.run(Thread.java:534)
      2003-10-24 11:44:43,709 DEBUG [org.apache.tomcat.util.net.PoolTcpEndpoint] Handshake failed
      javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA6275)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA6275)
      at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocketFactory.java:290)
      at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:540)
      at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
      at java.lang.Thread.run(Thread.java:534)
      Caused by: java.io.EOFException: SSL peer shut down incorrectly
      at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA6275)
      ... 7 more

      Thanks.

      • 2627 Views
      • Tags:
        • 1. Re: Problems with the authentication of the client in Jboss
          ljoncas
          ljoncas Oct 31, 2003 1:00 PM (in response to dgb)

          I had this same problem.

          For me, the solution was to tell JBoss/Tomcat where to find the server trust keystore (the keystore containing all the trusted client certs).

          Unfortunately the connector config in JBoss-Tomcat or in Tomcat does not let you specify this, so you have to find another way. Add the following parameter setting to your JVM startup for JBoss:

          -Djavax.net.ssl.trustStore=your_serverTrust_path


          By the way, Jetty seems to ignore this setting. I believe newer versions of Jetty support a property in the SunJsseListener config, but in the version bundled with JBoss 3.2.1 this wasn't available and a kludgy solution was described on the Jetty web site.

            • Actions
          • 2. Re: Problems with the authentication of the client in Jboss
            dgb
            dgb Nov 4, 2003 1:12 AM (in response to dgb)

            Thanks you.

              • Actions