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

"Manger, James H" <James.H.Manger@team.telstra.com> Thu, 06 May 2010 23:57 UTC

Return-Path: <James.H.Manger@team.telstra.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 EF32C3A69E5 for <oauth@core3.amsl.com>; Thu, 6 May 2010 16:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.223
X-Spam-Level: *
X-Spam-Status: No, score=1.223 tagged_above=-999 required=5 tests=[AWL=-0.477, BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
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 wmFWA98ve-ow for <oauth@core3.amsl.com>; Thu, 6 May 2010 16:57:49 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) by core3.amsl.com (Postfix) with ESMTP id 4DBF83A694E for <oauth@ietf.org>; Thu, 6 May 2010 16:57:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.52,344,1270389600"; d="scan'208,217";a="2482302"
Received: from unknown (HELO ipcdvi.tcif.telstra.com.au) ([10.97.217.212]) by ipocvi.tcif.telstra.com.au with ESMTP; 07 May 2010 09:57:33 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,5974"; a="1605461"
Received: from wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) by ipcdvi.tcif.telstra.com.au with ESMTP; 07 May 2010 09:57:34 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) with mapi; Fri, 7 May 2010 09:57:33 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: OAuth WG <oauth@ietf.org>
Date: Fri, 07 May 2010 09:57:32 +1000
Thread-Topic: Indicating sites where a token is valid
Thread-Index: Acrtd+RKgxK8uGQ7RkCGWfcUzOTj/g==
Message-ID: <255B9BB34FB7D647A506DC292726F6E11263073D6D@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_255B9BB34FB7D647A506DC292726F6E11263073D6DWSMSG3153Vsrv_"
MIME-Version: 1.0
Subject: [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: Thu, 06 May 2010 23:57:50 -0000

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