[
https://issues.apache.org/jira/browse/SLIDER-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14035981#comment-14035981
]
Steve Loughran commented on SLIDER-131:
---------------------------------------
splitting things up makes sense
# the web UI comes via the proxy, so is secured that way
# the REST API -if we set it up to work through the proxy can go the same way
with some SPNEGO auth.
# if we don't do that, again, security issues surface -which implies we may
want to think about having it on its own port too.
Owen pointed out to me yesterday, as SSL certificates are host-specific only,
not (hostname, port), to complicate things
> enable AM one and two-way SSL and test/enable agent secure comm
> ---------------------------------------------------------------
>
> Key: SLIDER-131
> URL: https://issues.apache.org/jira/browse/SLIDER-131
> Project: Slider
> Issue Type: Bug
> Components: agent, appmaster
> Reporter: Jonathan Maron
> Assignee: Jonathan Maron
>
> AM has ssl settings enabling SSL (including 2-way). Work through enabling
> this feature (perhaps initially testing it with a browser that has the
> appropriate server cert and client key), and subsequently try to ensure agent
> can communicate with server using both SSL modes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
