eclipse-ee4j / eclipse-ee4j/jersey
SSLContext not propagated to PoolingHttpClientConnectionManager
Open
Component: connectors
Priority: Major
Type: Bug
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
I'm migrating Jersey 1.x to 2.0 and I found that with had some issues with SSL.
I'm not using keystore in the client, instead I used : TrustManager and HostnameVerifier. If I use that, I'll obtain a javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed:...
I trace the code, and found that PoolingHttpClientConnectionManager was using a default SSLFactory instead of the SSLContext that I used for the client.
When I recreate PoolingHttpClientConnectionManager with my settings, it works. (the SSL handshake).
#### Affected Versions
[2.22.1]
Contributor guide
Assessment
This issue has not been assessed yet.