[CXF-8667] Custom certificate alias not being used when using HC5 AsyncHTTPConduit

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.6, 3.5.1
• Fix Version/s: 3.5.2, 3.4.7, 4.0.0
• Component/s: Transports
• Estimated Complexity: Unknown
• Assignee: Andriy Redko
• Reporter: Bastien Bouclet
• Created: 01/Mar/22 13:44
• Updated: 18/Sep/23 18:48
• Resolved: 19/Mar/22 21:28

Description

When using `org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduit` and setting `TLSClientParameters.certAlias` so the HTTP client sends a specific client certificate from the keystore, the certificate alias is ignored.

From what I've been able to debug, it seems `AsyncHTTPConduit` creates a `RegistryBuilder<TlsStrategy>` with the proper SSL settings but never actually registers them with the HTTP client:

https://github.com/apache/cxf/blob/1ecc24d817d4ef0cba4a4079a1c69abf33d1ad9b/rt/transports/http-hc5/src/main/java/org/apache/cxf/transport/http/asyncclient/hc5/AsyncHTTPConduit.java#L528

Issue Links

• is a clone of: CXF-8665 Custom certificate alias not being used when using HC AsyncHTTPConduit
• is blocked by: HTTPCLIENT-2209 Pass HttpContext to AsyncClientConnectionOperator
• is related to: CXF-8674 Custom SSLContext using async http-client5 does not work
• is related to: CXF-8678 Update to Apache HttpClient5 5.2