directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Riddering (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-2043) SSL connection failures errors are useless
Date Wed, 05 Oct 2016 12:02:20 GMT


Andreas Riddering commented on DIRSERVER-2043:

I could give it a try later on, if its possible to test this on the test-environment. But
as there are serveral hundrets of people using the prouctive env and as its configured with
HA stuff and so on, it won't be possible to change this within a short matter of time.

I am just wondering, why ADS is working fine with an older Java-Version, but refuses to connect
to the same server when working with a newer version. There must be something, thats taking
into account?!?

As i did some testing, your supposal with TLSv1.1 could solve our problem. I tried to connect
to the (older) server with tls1_1 via openssl, and it didnt work. Using a newer server, which
supports TLS1.1 and 1.2 can be connected to via ADS and newer JavaVersion.

So, is it possible to start ADS (with newer Java Version) with TLS1(.0) Support enabled?
For the short term it only needs to use the older java version or has tls1(.0) support enabled.
Couldn't find out how this is possible...

> SSL connection failures errors are useless
> ------------------------------------------
>                 Key: DIRSERVER-2043
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M19
>            Reporter: Roy Wellington
>            Priority: Minor
> When connecting, if StartTLS fails, you get an error such as the following:
> {noformat}
> Error while opening connection
>  - SSL handshake failed.
> SSL handshake
> 	at
> 	at
> 	at
> 	at$
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> SSL handshake failed.
> {noformat}
> But _why_ did the SSL handshake fail? I don't need the stack trace, I need to know what
exactly failed, something like what Firefox/Chrome do on SSL failures. I'm trying to debug
this right now, and I have absolutely no idea what's going on here.

This message was sent by Atlassian JIRA

View raw message