[
https://issues.apache.org/jira/browse/MESOS-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941870#comment-15941870
]
Greg Mann commented on MESOS-6304:
----------------------------------
{code}
commit 0fea4c5fb4ab785cf8c6d6db9e288391a8705e65
Author: Greg Mann <[email protected]>
Date: Sat Mar 25 12:04:14 2017 -0700
Added support for auth tokens to the default executor.
This patch updates the default executor to extract
an authentication token from its environment when present,
and use this token to authenticate with the agent.
Review: https://reviews.apache.org/r/57808/
{code}
{code}
commit dfdd9bde5f67861a19083d0a173e683ec569fb63
Author: Greg Mann <[email protected]>
Date: Sat Mar 25 12:04:11 2017 -0700
Added support for auth tokens to the V1 executor library.
This patch adds support for authentication tokens to the
V1 default executor library. The tokens are loaded from a
pre-determined environment variable, if present.
Review: https://reviews.apache.org/r/57615/
{code}
> 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
> Fix For: 1.3.0
>
>
> 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)
