[jira] [Comment Edited] (MESOS-3753) Test the HTTP Scheduler library with SSL enabled

["Greg Mann (JIRA)" <ji...@apache.org>]

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

Greg Mann edited comment on MESOS-3753 at 8/10/16 10:41 PM:
------------------------------------------------------------

Reviews to add SSL support to one of the scheduler tests here:
https://reviews.apache.org/r/50969/
https://reviews.apache.org/r/50857/

Note that more comprehensive libprocess-level tests of SSL behavior can be found in MESOS-5966


was (Author: greggomann):
Reviews to add SSL support to one of the scheduler tests here:
https://reviews.apache.org/r/50969/
https://reviews.apache.org/r/50857/

> Test the HTTP Scheduler library with SSL enabled
> ------------------------------------------------
>
>                 Key: MESOS-3753
>                 URL: https://issues.apache.org/jira/browse/MESOS-3753
>             Project: Mesos
>          Issue Type: Story
>          Components: framework, HTTP API, test
>            Reporter: Joseph Wu
>            Assignee: Greg Mann
>              Labels: mesosphere, security
>
> Currently, the HTTP Scheduler library does not support SSL-enabled Mesos.  
> (You can manually test this by spinning up an SSL-enabled master and attempt to run the event-call framework example against it.)
> We need to add tests that check the HTTP Scheduler library against SSL-enabled Mesos:
> * with downgrade support,
> * with required framework/client-side certifications,
> * with/without verification of certificates (master-side),
> * with/without verification of certificates (framework-side),
> * with a custom certificate authority (CA)
> These options should be controlled by the same environment variables found on the [SSL user doc|http://mesos.apache.org/documentation/latest/ssl/].
> Note: This issue will be broken down into smaller sub-issues as bugs/problems are discovered.



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