Re: [OAUTH-WG] Oauth Server to Server

Phil Hunt <phil.hunt@oracle.com> Tue, 24 September 2013 16:05 UTC

Return-Path: <phil.hunt@oracle.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 75BF721F967F for <oauth@ietfa.amsl.com>; Tue, 24 Sep 2013 09:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.547
X-Spam-Level:
X-Spam-Status: No, score=-4.547 tagged_above=-999 required=5 tests=[AWL=-1.799, BAYES_00=-2.599, FRT_ADOBE2=2.455, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6t9wHZZe2y3u for <oauth@ietfa.amsl.com>; Tue, 24 Sep 2013 09:05:48 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 50D2511E8169 for <oauth@ietf.org>; Tue, 24 Sep 2013 09:05:32 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r8OG5MCG013434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 24 Sep 2013 16:05:23 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r8OG5LAN025403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Sep 2013 16:05:22 GMT
Received: from abhmt114.oracle.com (abhmt114.oracle.com [141.146.116.66]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r8OG5LM7013521; Tue, 24 Sep 2013 16:05:21 GMT
Received: from [192.168.1.125] (/24.86.29.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 24 Sep 2013 09:05:20 -0700
References: <832FA2A6-D0DD-45D0-9107-7EE02B6793B7@adobe.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <832FA2A6-D0DD-45D0-9107-7EE02B6793B7@adobe.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <02B18626-39F5-4AC5-9AB9-DBB580428946@oracle.com>
X-Mailer: iPhone Mail (11A465)
From: Phil Hunt <phil.hunt@oracle.com>
Date: Tue, 24 Sep 2013 09:05:17 -0700
To: Antonio Sanso <asanso@adobe.com>
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Oauth Server to Server
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Sep 2013 16:05:53 -0000

Just looking at your subject line, and I may have this wrong but are you not asking about chaining? In server to server you need a way for the second server to accept a token from the first to propagate the authorization correct?

Phil

> On Sep 24, 2013, at 5:08, Antonio Sanso <asanso@adobe.com> wrote:
> 
> Hi *,
> 
> apologis to be back to this argument :).
> 
> Let me try to better explain one use case that IMHO would be really good to have in the OAuth specification family :)
> 
> At the moment the only "OAuth standard" way I know to do OAuth server to server is to use [0] namely Resource Owner Password Credentials Grant.
> 
> Let me tell I am not a big fun of this particular flow :) (but this is another story).
> 
> An arguable better way to solve this scenario is to user (and why not to standardise :S?) the method used by Google (or a variant of it) see [1].
> 
> Couple of more things:
> 
> - I do not know if Google would be interested to put some effort to standardise it (is anybody from Google lurking :) e.g.Tim Bray :D )
> - I am not too familiar with IETF process. Would the OAuth WG take in consideration such proposal draft??
> 
> Thanks and regards
> 
> Antonio
> 
> [0] http://tools.ietf.org/html/rfc6749#section-4.3
> [1] https://developers.google.com/accounts/docs/OAuth2ServiceAccount
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth