[
https://issues.apache.org/jira/browse/HTTPCORE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376277#comment-17376277
]
Oleg Kalnichevski commented on HTTPCORE-682:
--------------------------------------------
[~pveselov] Does not {{SSLContextBuilder}} already provide a means of selecting
a particular security provider? [1] Is something still lacking?
In any way you are welcome to submit the changes you are proposing as a PR at
GitHub. This is the easiest and fastest way of getting things done.
Oleg
[1]
http://hc.apache.org/httpcomponents-core-5.1.x/current/httpcore5/apidocs/org/apache/hc/core5/ssl/SSLContextBuilder.html#setProvider(java.security.Provider)
> Should be possible to specify the provider for key manager/trust manager
> ------------------------------------------------------------------------
>
> Key: HTTPCORE-682
> URL: https://issues.apache.org/jira/browse/HTTPCORE-682
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Components: HttpCore
> Affects Versions: 4.4.14, 5.1
> Reporter: Pawel Veselov
> Priority: Major
>
> {{SSLContextBuilder}} always uses default {{getInstance()}} method to get the
> trust or key manager factory. Unlike {{SSLContext}} that supports having a
> provider explicitly specified.
> Since there is no way to specify trust or key managers explicitly, the only
> way to make a desired trust manager load is to meddle with the security
> providers, which is not always desirable or possible.
> So, it would be great if the SSL context builder allowed for either of:
> * Use currently specified (using {{setProvider()}}) provider/provider name
> when loading trust/key managers
> * Support specifying the provider for trust/key managers explicitly
> * Support specifying trust managers or key managers explicitly
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
