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

Gary Gregory updated HTTPCORE-450:
----------------------------------
    Description: 
Add a provider parameter in {{SSLContextBuilder}} to support third party 
provider such as The Legion of the Bouncy Castle 
(https://www.bouncycastle.org/java.html).

New APIs:
- {{org.apache.http.ssl.SSLContextBuilder.setProvider(Provider)}} in release 
5.0-alpha3 and 4.4.7 (upcoming)
- {{org.apache.http.ssl.SSLContextBuilder.setProvider(String)}} in release 
5.0-alpha4 (upcoming)

  was:
Add a provider parameter in {{SSLContextBuilder}} to support third party 
provider such as The Legion of the Bouncy Castle 
(https://www.bouncycastle.org/java.html).

New APIs:
- {{org.apache.http.ssl.SSLContextBuilder.setProvider(Provider)}} in release 
5.0-alpha3
- {{org.apache.http.ssl.SSLContextBuilder.setProvider(String)}} in release 
5.0-alpha4 (upcoming)


> Add a Provider parameter in SSLContextBuilder
> ---------------------------------------------
>
>                 Key: HTTPCORE-450
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-450
>             Project: HttpComponents HttpCore
>          Issue Type: New Feature
>    Affects Versions: 4.4.6
>            Reporter: lujianbo
>            Assignee: Gary Gregory
>              Labels: features
>             Fix For: 4.4.7, 5.0-alpha3, 5.0-alpha4
>
>
> Add a provider parameter in {{SSLContextBuilder}} to support third party 
> provider such as The Legion of the Bouncy Castle 
> (https://www.bouncycastle.org/java.html).
> New APIs:
> - {{org.apache.http.ssl.SSLContextBuilder.setProvider(Provider)}} in release 
> 5.0-alpha3 and 4.4.7 (upcoming)
> - {{org.apache.http.ssl.SSLContextBuilder.setProvider(String)}} in release 
> 5.0-alpha4 (upcoming)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to