IETF Logo Mail Archive

Re: [OAUTH-WG] Issue: Scope parameter

"Manger, James H" <James.H.Manger@team.telstra.com> Fri, 16 April 2010 13:58 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 0A16828C151 for <oauth@core3.amsl.com>; Fri, 16 Apr 2010 06:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.736
X-Spam-Level:
X-Spam-Status: No, score=0.736 tagged_above=-999 required=5 tests=[AWL=-0.777, BAYES_40=-0.185, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, 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 4S8MqHg4cLPI for <oauth@core3.amsl.com>; Fri, 16 Apr 2010 06:58:32 -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 D23A33A6C4F for <oauth@ietf.org>; Fri, 16 Apr 2010 06:54:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.52,219,1270389600"; d="scan'208";a="1243121"
Received: from unknown (HELO ipcdvi.tcif.telstra.com.au) ([10.97.217.212]) by ipocvi.tcif.telstra.com.au with ESMTP; 16 Apr 2010 23:54:31 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,5952"; a="800195"
Received: from wsmsg3701.srv.dir.telstra.com ([172.49.40.169]) by ipcdvi.tcif.telstra.com.au with ESMTP; 16 Apr 2010 23:54:32 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3701.srv.dir.telstra.com ([172.49.40.169]) with mapi; Fri, 16 Apr 2010 23:54:31 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Mark Mcgloin <mark.mcgloin@ie.ibm.com>, OAuth WG <oauth@ietf.org>
Date: Fri, 16 Apr 2010 23:54:29 +1000
Thread-Topic: [OAUTH-WG] Issue: Scope parameter
Thread-Index: AcrdaXa9LgztGtXQSgCHbQtfbIzDcAAAGYeg
Message-ID: <255B9BB34FB7D647A506DC292726F6E112575922E6@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E11257591E3F@WSMSG3153V.srv.dir.telstra.com> <OF70542F9E.35EC96CC-ON80257707.003656F0-80257707.004A7B66@ie.ibm.com>
In-Reply-To: <OF70542F9E.35EC96CC-ON80257707.003656F0-80257707.004A7B66@ie.ibm.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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Issue: Scope parameter
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: Fri, 16 Apr 2010 13:58:33 -0000

Mark,

> James, how does your proposal work if the client needs access
> to more than one set of resources?

I think a client app will need service-specific knowledge to realise it needs access to more than one set of resources (ie the app needs to know how the service divides resources into sets). That service-specific knowledge may as well include the service-specific authz URIs for requesting access to multiple sets of resources. http://as.com/foo,bar/, for instance.

If a client with a token for one scope tries to accesses a resource in a second scope, the 401 response could include an authz URI indicating both scopes.


-- 
James Manger

v2.23.0 | Report a Bug | By Email