[arquillian-issues] [JBoss JIRA] (ARQ-1370) Warp: support SSL for CommandService using untrusted communication

[Oliver Bock (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765586#comment-12765586 ] 

Oliver Bock commented on ARQ-1370:
----------------------------------

Sure, you're welcome.

Regarding your proposed solution (referenced in the description): without admittedly knowing Warp's internals, this looks more like a workaround than a solution. The root cause of this problem seems to be that {{Alpha3}} requires a dedicated custom SSL context (or TrustManager, respectively) while {{Alpha2}} was able to make use of the container's existing SSL context as described in ARQ-1365 and the forum thread (referenced above). The question is: why is that and would it be possible to let {{CommandService}} reuse the existing SSL context as well? Just ignore my comment if I'm totally mistaken ;-)

                
> Warp: support SSL for CommandService using untrusted communication
> ------------------------------------------------------------------
>
>                 Key: ARQ-1370
>                 URL: https://issues.jboss.org/browse/ARQ-1370
>             Project: Arquillian
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Warp
>    Affects Versions: warp_1.0.0.Alpha3
>            Reporter: Lukáš Fryč
>
> We can make use of HTTP client which will automatically trust SSL endpoint.
> http://stackoverflow.com/questions/2703161/how-to-ignore-ssl-certificate-errors-in-apache-httpclient-4-0

--
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