Re: [OAUTH-WG] [token-exchange] exchanging between issuers/domains

Bill Burke <bburke@redhat.com> Fri, 28 July 2017 15:06 UTC

Return-Path: <bburke@redhat.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8AC7131CA4 for <oauth@ietfa.amsl.com>; Fri, 28 Jul 2017 08:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.923
X-Spam-Level:
X-Spam-Status: No, score=-6.923 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eIqQociCdkC0 for <oauth@ietfa.amsl.com>; Fri, 28 Jul 2017 08:06:50 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20483131D24 for <oauth@ietf.org>; Fri, 28 Jul 2017 08:06:49 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 056D05C167 for <oauth@ietf.org>; Fri, 28 Jul 2017 15:06:49 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 056D05C167
Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=bburke@redhat.com
Received: from ovpn-116-148.phx2.redhat.com (ovpn-116-148.phx2.redhat.com [10.3.116.148]) by smtp.corp.redhat.com (Postfix) with ESMTP id C0FBF6C20A for <oauth@ietf.org>; Fri, 28 Jul 2017 15:06:48 +0000 (UTC)
To: oauth@ietf.org
References: <1b5f403e-aa93-3cfe-ab39-a471cf864e5d@redhat.com>
From: Bill Burke <bburke@redhat.com>
Message-ID: <46fff444-9107-7a43-1854-88c92aaccd90@redhat.com>
Date: Fri, 28 Jul 2017 11:06:48 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <1b5f403e-aa93-3cfe-ab39-a471cf864e5d@redhat.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Fri, 28 Jul 2017 15:06:49 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/mMMNyVSRXoiVuUClZaN-Y-f4deI>
Subject: Re: [OAUTH-WG] [token-exchange] exchanging between issuers/domains
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 15:06:52 -0000

Should probably have a "subject_issuer" and "actor_issuer" as well as 
the "requested_issuer" too.

FYI, I'm actually applying this spec to write a token exchange service 
to connect various product stacks that have different and often 
proprietary token formats and architectures.


On 7/26/17 6:44 PM, Bill Burke wrote:
> Hi all,
>
> I'm looking at Draft 9 of the token-exchange spec.  How would one 
> build a request to:
>
> * exchange a token issued by a different domain to a client managed by 
> the authorization server.
>
> * exchange a token issued by the authorization server (the STS) for a 
> token of a different issuer and different client.  In other words, for 
> a token targeted to a specific client in a different authorization 
> server or realm or domain or whatever you want to call it.
>
> * exchange a token issued by a different issuer for a token of a 
> different issuer and client.
>
> Is the spec missing something like a "requested_issuer" identifier?  
> Seems that audience is too opaque of a parameter for the authz server 
> to determine how to exchange the token.
>
> Thanks,
>
> Bill
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth