You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Greg Mann (JIRA)" <ji...@apache.org> on 2017/03/15 23:47:41 UTC
[jira] [Comment Edited] (MESOS-6304) Add authentication support to
the default executor
[ https://issues.apache.org/jira/browse/MESOS-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927075#comment-15927075 ]
Greg Mann edited comment on MESOS-6304 at 3/15/17 11:47 PM:
------------------------------------------------------------
Review here:
https://reviews.apache.org/r/57615/
Tests for this functionality will be included in the patches for MESOS-6998
was (Author: greggomann):
Review here:
https://reviews.apache.org/r/57615/
> Add authentication support to the default executor
> --------------------------------------------------
>
> Key: MESOS-6304
> URL: https://issues.apache.org/jira/browse/MESOS-6304
> Project: Mesos
> Issue Type: Improvement
> Components: executor, modules, security
> Reporter: Galen Pewtherer
> Assignee: Greg Mann
> Labels: executor, mesosphere, module, security
>
> The V1 executors should be updated to authenticate with the agent when HTTP executor authentication is enabled. This will be hard-coded into the executor library for the MVP, and it can be refactored into an {{HttpAuthenticatee}} module later. The executor must:
> * load a JWT from its environment, if present
> * decorate its requests with an {{Authorization}} header containing the JWT
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)