[jira] [Resolved] (CXF-8665) Custom certificate alias not being used when using HC AsyncHTTPConduit

["Andriy Redko (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andriy Redko resolved CXF-8665.
-------------------------------
    Resolution: Won't Fix

Should be fixed by CXF-8673

> Custom certificate alias not being used when using HC AsyncHTTPConduit
> ----------------------------------------------------------------------
>
>                 Key: CXF-8665
>                 URL: https://issues.apache.org/jira/browse/CXF-8665
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.5.0, 3.3.6
>            Reporter: Bastien Bouclet
>            Priority: Major
>
> When using `org.apache.cxf.transport.http.asyncclient.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` sets the SSL settings to be used in the http client context attribute `http.iosession-factory-registry`:
> [https://github.com/apache/cxf/blob/e758de3e60501bd33ca1b9ef3df685128d4a443a/rt/transports/http-hc/src/main/java/org/apache/cxf/transport/http/asyncclient/AsyncHTTPConduit.java#L564]
> However, the http client is using the context attribute `http.ioSession-factory-registry` (note the different capitalisation) (org.apache.http.protocol.BasicHttpContext is case sensitive):
> [https://github.com/apache/httpasyncclient/blob/0f491c178be95114122957aa60e64f347d965e73/httpasyncclient/src/main/java/org/apache/http/impl/nio/conn/PoolingNHttpClientConnectionManager.java#L100]
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)