Hi Chris,
thank you for your reply!
On the tomcat everything works fine, I can see that the client certificate
is checked via my JSSE-Implementation in both cases!
This is the stacktrace from my test:
java.net.SocketException: Software caused connection abort: socket write
error
at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nancee,
On 1/10/14, 5:28 AM, Nancee Riehl wrote:
thank you for your reply! On the tomcat everything works fine, I
can see that the client certificate is checked via my
JSSE-Implementation in both cases!
This is the stacktrace from my test:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nancee,
On 1/8/14, 4:56 AM, Nancee Riehl wrote:
Is this the right mailing-list for my question?
Yes! Welcome.
I'm writing a JUNIT-Test to test a connection to tomcat 7.0.47
over HTTPS/TLSv1.1 with a corrupted Client-Certificate.
When I run
Hi all,
I'm writing a JUNIT-Test to test a connection to tomcat 7.0.47 over
HTTPS/TLSv1.1 with a corrupted Client-Certificate.
When I run my test against a remote tomcat everything works fine, I get an
SSLHandshakeException.
When I run the same test against a local tomcat I get this error:
