[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390351#comment-15390351
 ] 

ASF GitHub Bot commented on HTTPCLIENT-1752:
--------------------------------------------

GitHub user simonetripodi opened a pull request:

    https://github.com/apache/httpclient/pull/56

    HTTPCLIENT-1752 - Allow to configure the OSGI clients with relaxed SSL 
checks

    This is my proposal to add HTTPCLIENT-1752 feture.
    Feedbacks, suggestions, hints, ... are always welcome!

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/simonetripodi/httpclient trunk

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/httpclient/pull/56.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #56
    
----
commit 7567ee748ce8894846e4cf2f9be2cd34d04c7f38
Author: Simo Tripodi <[email protected]>
Date:   2016-07-21T12:02:27Z

    HTTPCLIENT-1752 - Allow to configure the OSGI clients with relaxed SSL 
checks
    
    initial prototype check-in

commit 3da238b77b6f8dd337ffb5337b1035f45e9ee19b
Author: Simo Tripodi <[email protected]>
Date:   2016-07-22T12:39:42Z

    HTTPCLIENT-1752 - Allow to configure the OSGI clients with relaxed SSL
    checks
    
    added a flag to mark a trusted hosts configuration is enabled or not

commit 6ab5922b25775b7de12fd324133d7449cbf56aba
Author: Simo Tripodi <[email protected]>
Date:   2016-07-22T16:13:27Z

    HTTPCLIENT-1752 - Allow to configure the OSGI clients with relaxed SSL
    checks
    
    TrustedHostConfiguration made as a Managed Service
    All component finally wired
    Minor OSGi dependencies adjustments

commit 53fa440376d03a993c29934859ecb048d1531904
Author: Simo Tripodi <[email protected]>
Date:   2016-07-22T16:16:36Z

    HTTPCLIENT-1752 - Allow to configure the OSGI clients with relaxed SSL
    checks
    
    too many deleted entries

commit f591f78250e6bb00db48a6b50a2a3702b422021e
Author: Simo Tripodi <[email protected]>
Date:   2016-07-22T22:54:29Z

    HTTPCLIENT-1752 - Allow to configure the OSGI clients with relaxed SSL
    checks
    
    fixed configuration manager labels

commit f11b3c189798fbe5c7e4243bcdb62947db36ed85
Author: Simo Tripodi <[email protected]>
Date:   2016-07-22T23:01:39Z

    releng: PIDs aligned to `client5` convention so they don't collide in a
    system where the older http client version is installed

commit da572a1c91c9b3ade86fde7a462457431dafb348
Author: Simo Tripodi <[email protected]>
Date:   2016-07-22T23:14:41Z

    HTTPCLIENT-1752 - Allow to configure the OSGI clients with relaxed SSL
    checks
    
    added TrustedHostsConfiguration tests

----


> Allow to configure the OSGI clients with relaxed SSL checks
> -----------------------------------------------------------
>
>                 Key: HTTPCLIENT-1752
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1752
>             Project: HttpComponents HttpClient
>          Issue Type: New Feature
>          Components: HttpClient
>    Affects Versions: 4.5.2
>            Reporter: Timothee Maret
>            Assignee: Simone Tripodi
>             Fix For: Future
>
>         Attachments: HTTPCLIENT-1752_initial.patch
>
>
> In deployments other than production (e.g. dev, qa, integration testing, 
> etc.) it is often useful to deploy self-signed certificates instead of 
> certificates signed by a trusted CA for cost and simplicity reasons.
> By default, the http client does not validate a self signed certificate 
> because it is not signed by a trusted CA root. 
> One way to have the http client to validate the self signed certificate is to 
> add the self-signed certificate (or the detached CA root that signed it) in 
> the java trustore.
> This operation is a configuration only change (no need to change code) 
> however it typically requires accessing the FS and the scope of trust can't 
> be easily modified at runtime.
> Another way to have the http client to validate the self signed certificate 
> is to use the TrustSelfSignedStrategy [0] strategy when building the http 
> client.
> This requires modifying the code.
> In order to use the second approach without modifying code, it would be 
> interesting to allow configuring a set of URIs for which the relaxed SSL mode 
> should be used.
> The configuration could be implemented similarly to the implementation of the 
> central prox configuration (OSGI) in HTTPCLIENT-1238. In addition to allowing 
> sel-signed certificates, the configuration could as well allow to skip FQDN 
> check using the NoopHostnameVerifier [1].
> Of course, this feature *must not* be deployed in production environment as 
> it is totally insecure.
> [0] 
> https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/ssl/TrustSelfSignedStrategy.html
> [1] 
> https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/ssl/NoopHostnameVerifier.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to