Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
3.4.6, 3.5.1
-
None
-
Unknown
Description
AsyncHTTPConduit configures httpclient5 tlsstrategy here
however this configuration is actually never used. Instead, the http-client5 is always built using the system default TlsStrategy here
The result is that custom SSLContext configured in the httpconduit is not honored.
The current workaround is to keep using cxf-rt-transports-http-hc, or force using the sync httpclient.
I did a quick test propagating the RegistryBuilder<TlsStrategy> built at AsyncHTTPConduit up until the httpclient is built and the custom SSLContext started being used.
Attachments
Issue Links
- relates to
-
CXF-8667 Custom certificate alias not being used when using HC5 AsyncHTTPConduit
- Closed