Re: [OAUTH-WG] OAuth 2.0 server behavior
Eran Hammer-Lahav <eran@hueniverse.com> Mon, 29 November 2010 16:39 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 764D528C0F0 for <oauth@core3.amsl.com>; Mon, 29 Nov 2010 08:39:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.607
X-Spam-Level:
X-Spam-Status: No, score=-1.607 tagged_above=-999 required=5 tests=[AWL=-0.868, BAYES_20=-0.74, 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 r+bRHfUD0Hkx for <oauth@core3.amsl.com>; Mon, 29 Nov 2010 08:39:55 -0800 (PST)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 0DAFD28C104 for <oauth@ietf.org>; Mon, 29 Nov 2010 08:39:50 -0800 (PST)
Received: (qmail 26436 invoked from network); 29 Nov 2010 16:40:59 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 29 Nov 2010 16:40:59 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Mon, 29 Nov 2010 09:40:50 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Anton Panasenko <anton.panasenko@gmail.com>, "oauth@ietf.org" <oauth@ietf.org>
Date: Mon, 29 Nov 2010 09:40:55 -0700
Thread-Topic: [OAUTH-WG] OAuth 2.0 server behavior
Thread-Index: AcuP4/CCziQ8p1elQMy+nRNAmYA08gAADNAw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343D4B06552C@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <5F4958F3-F1C5-4E0E-9AE4-7042C5EA1AAC@gmail.com>
In-Reply-To: <5F4958F3-F1C5-4E0E-9AE4-7042C5EA1AAC@gmail.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_90C41DD21FB7C64BB94121FBBC2E72343D4B06552CP3PW5EX1MB01E_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] OAuth 2.0 server behavior
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: Mon, 29 Nov 2010 16:39:58 -0000
#2. Asking for scope on the access token call can only reduce the already approved scope. EHL From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Anton Panasenko Sent: Friday, November 26, 2010 10:54 AM To: oauth@ietf.org Subject: [OAUTH-WG] OAuth 2.0 server behavior Hi, What behavior is expected from the server, if in the query on access_token without "scope" (grant_type=authorization_code&client_id=s6BhdRkqt3&client_secret=gX1fBat3bV&code=i1WsRn1uB1&redirect_uri=https%3A%2F%2Fclient%2Eexample%2Ecom%2Fc)? 1. The server must generate access_token for an empty scope. 2. The server must generate access_token for scope, which was approved for access_code. -- Sincerely yours Anton Panasenko Skype: anton.panasenko Phone: +79179838291 Email: anton.panasenko@gmail.com<mailto:anton.panasenko@gmail.com>, apanasenko@me.com<mailto:apanasenko@me.com>
- [OAUTH-WG] OAuth 2.0 server behavior Anton Panasenko
- Re: [OAUTH-WG] OAuth 2.0 server behavior Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth 2.0 server behavior Subbu Allamaraju
- Re: [OAUTH-WG] OAuth 2.0 server behavior Eran Hammer-Lahav