You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andriy Redko (Jira)" <ji...@apache.org> on 2022/03/19 21:29:00 UTC
[jira] [Resolved] (CXF-8667) Custom certificate alias not being used when using HC5 AsyncHTTPConduit
[ https://issues.apache.org/jira/browse/CXF-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andriy Redko resolved CXF-8667.
-------------------------------
Resolution: Fixed
> Custom certificate alias not being used when using HC5 AsyncHTTPConduit
> -----------------------------------------------------------------------
>
> Key: CXF-8667
> URL: https://issues.apache.org/jira/browse/CXF-8667
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.4.6, 3.5.1
> Reporter: Bastien Bouclet
> Assignee: Andriy Redko
> Priority: Major
> Fix For: 3.5.2, 3.4.7, 4.0.0
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.1#820001)