Re: [OAUTH-WG] Indicating sites where a token is valid

Eran Hammer-Lahav <eran@hueniverse.com> Sun, 09 May 2010 21:30 UTC

Return-Path: <eran@hueniverse.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 015F93A69CE for <oauth@core3.amsl.com>; Sun, 9 May 2010 14:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.713
X-Spam-Level:
X-Spam-Status: No, score=-1.713 tagged_above=-999 required=5 tests=[AWL=-0.604, BAYES_05=-1.11, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pFAN5RQxJy9 for <oauth@core3.amsl.com>; Sun, 9 May 2010 14:30:09 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 624C13A6917 for <oauth@ietf.org>; Sun, 9 May 2010 14:30:09 -0700 (PDT)
Received: (qmail 18261 invoked from network); 9 May 2010 21:29:57 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 9 May 2010 21:29:57 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Sun, 9 May 2010 14:29:57 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>, OAuth WG <oauth@ietf.org>
Date: Sun, 9 May 2010 14:29:58 -0700
Thread-Topic: Indicating sites where a token is valid
Thread-Index: Acrtd+RKgxK8uGQ7RkCGWfcUzOTj/gCRtgSg
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3AB46E20@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <255B9BB34FB7D647A506DC292726F6E11263073D6D@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E11263073D6D@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_90C41DD21FB7C64BB94121FBBC2E72343B3AB46E20P3PW5EX1MB01E_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Indicating sites where a token is valid
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 09 May 2010 21:30:11 -0000

Add some sort of wildcard support and I think this looks good.

EHL

From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Manger, James H
Sent: Thursday, May 06, 2010 4:58 PM
To: OAuth WG
Subject: [OAUTH-WG] Indicating sites where a token is valid

The OAuth2 protocol does not indicate where a token can be used.
It needs to do so because if a client app sends a token to the wrong site it destroys the security.

I suggest another field in the JSON token response:
  "sites": ["https://api.example.com", "http://photo.example.com:8080"]

It would be a list of sites where the token can be used, specified by scheme://host[:port].

The default value for the “sites” field could be the token endpoint site (or the authorization endpoint site if a token endpoint isn’t used).
For instance, if Facebook’s new API uses https://graph.facebook.com for all resources, tokens, and authorizations it could omit the “sites” field.


P.S. I suggested this last month http://www.ietf.org/mail-archive/web/oauth/current/msg01920.html,  though I mixed in additional ideas for formats and media type that are probable best covered in their own treads.


--
James Manger