[
https://issues.apache.org/jira/browse/HTTPCORE-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski moved HTTPASYNC-89 to HTTPCORE-396:
-----------------------------------------------------
Affects Version/s: (was: 4.0.2)
4.4
Issue Type: Bug (was: Improvement)
Key: HTTPCORE-396 (was: HTTPASYNC-89)
Project: HttpComponents HttpCore (was: HttpComponents
HttpAsyncClient)
> Add SSLContextBuilder for HttpAsyncClient
> -----------------------------------------
>
> Key: HTTPCORE-396
> URL: https://issues.apache.org/jira/browse/HTTPCORE-396
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Affects Versions: 4.4
> Reporter: Chris Kistner
> Priority: Minor
> Labels: SSLContext, SSLEngine, X509ExtendedKeyManager
> Attachments: ApacheAsyncPrivateKeyStrategy.java,
> ApacheAsyncSSLContextBuilder.java
>
>
> I tried using httpclient-4.3.6's SSLContextBuilder to build a SSLContext,
> which I then fed to my AsyncHttpClient connection pool.
> It worked just fine for configuring the cipher suites, TLS/SSL protocols and
> trust stores, however it did not work for the key managers.
> The reason being that it did not implement a key manager that extended
> X509ExtendedKeyManager.
> As far as I saw the differences between the X509ExtendedKeyManager abstract
> class and X509KeyManager interface are:
> * X509ExtendedKeyManager (for async [and sync]) takes in SSLEngine as
> argument for its chooseEngineClientAlias method
> * X509KeyManager (for sync only) takes in Socket as argument for its
> chooseServerAlias method
> For the while being, I've copied and adjusted the SSLContextBuilder and
> PrivateKeyStrategy classes to suite my needs for a KeyManager implementation
> when going async. See the attached files for my copy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
