Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4FB76200C28 for ; Mon, 13 Mar 2017 21:08:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4E442160B5D; Mon, 13 Mar 2017 20:08:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 96F6D160B6C for ; Mon, 13 Mar 2017 21:08:45 +0100 (CET) Received: (qmail 44354 invoked by uid 500); 13 Mar 2017 20:08:44 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 44345 invoked by uid 99); 13 Mar 2017 20:08:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Mar 2017 20:08:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5CE841AF9F4 for ; Mon, 13 Mar 2017 20:08:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.651 X-Spam-Level: X-Spam-Status: No, score=0.651 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id e38r7pefwt3o for ; Mon, 13 Mar 2017 20:08:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 5A908618AA for ; Mon, 13 Mar 2017 20:08:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 59894E05C1 for ; Mon, 13 Mar 2017 20:08:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id B8306243AE for ; Mon, 13 Mar 2017 20:08:41 +0000 (UTC) Date: Mon, 13 Mar 2017 20:08:41 +0000 (UTC) From: "Greg Mann (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MESOS-6304) Add authentication support to the default executor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 13 Mar 2017 20:08:46 -0000 [ https://issues.apache.org/jira/browse/MESOS-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann updated MESOS-6304: ----------------------------- Description: 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 was: The default executor should be updated to authenticate with the agent when HTTP executor authentication is enabled. This will be hard-coded into the default executor for the MVP. The executor must: * load the JWT from its environment, if present * decorate its requests with an {{Authorization}} header containing the JWT > 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)