[
https://issues.apache.org/jira/browse/CXF-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681584#comment-13681584
]
Daniel Kulp commented on CXF-5071:
----------------------------------
At the moment, CXF HTTP Conduits cannot have a specific SSLContext configured.
You either need all the settings so CXF can create it or the SocketFactory.
That said, I'd certainly be OK with adding a setting to have an SSLContext
configured in.
> Async Http transport: Injecting an sslSocketFactory in the
> tlsClientParameters has no effect
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-5071
> URL: https://issues.apache.org/jira/browse/CXF-5071
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.7.5
> Reporter: Aymeric Levaux
>
> When using the async http transport, the sslSocketFactory injected in the
> tlsClientParameters is not taken into account.
> TLSClientParameters.getSSLSocketFactory() is only used in
> HttpsURLConnectionFactory.
> This issue prevents the integration with custom JSSE implementations (e.g.:
> using the Websphere JSSEHelper to get a specific SSLSocketFactory).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
