Re: [OAUTH-WG] Client cannot specify the token type it needs

zhou.sujing@zte.com.cn Mon, 21 January 2013 05:18 UTC

Return-Path: <zhou.sujing@zte.com.cn>
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 515BA21F8518; Sun, 20 Jan 2013 21:18:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.395
X-Spam-Level:
X-Spam-Status: No, score=-98.395 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8O2u1vBgpWS; Sun, 20 Jan 2013 21:18:49 -0800 (PST)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8D421F850F; Sun, 20 Jan 2013 21:18:48 -0800 (PST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id CC77D1261C34; Mon, 21 Jan 2013 13:21:17 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r0L5IP59015238; Mon, 21 Jan 2013 13:18:25 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <1358744919.12881.YahooMailNeo@web31811.mail.mud.yahoo.com>
To: William Mills <wmills_92105@yahoo.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFCCDF8F10.8CEE85DE-ON48257AFA.001CFDB1-48257AFA.001D2C4E@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Mon, 21 Jan 2013 13:18:24 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-01-21 13:18:28, Serialize complete at 2013-01-21 13:18:28
Content-Type: multipart/alternative; boundary="=_alternative 001D2C4D48257AFA_="
X-MAIL: mse01.zte.com.cn r0L5IP59015238
Cc: "oauth@ietf.org WG" <oauth@ietf.org>, oauth-bounces@ietf.org
Subject: Re: [OAUTH-WG] Client cannot specify the token type it needs
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: Mon, 21 Jan 2013 05:18:50 -0000

The token type shoulbe decided by resource server, which consumes access 
token.
Client just re-tell the requested token type to AS. 
Client should not specify the token type.


oauth-bounces@ietf.org 写于 2013-01-21 13:08:39:

> This is true.  It's possible for the AS to vary it's behavior on 
> scope name, but it's presumed the AS and RS have an agreement of 
> what token type is in play.  Likely a good extension to the spec.
> 
> From: Prabath Siriwardena <prabath@wso2.com>
> To: "oauth@ietf.org WG" <oauth@ietf.org> 
> Sent: Sunday, January 20, 2013 7:28 PM
> Subject: [OAUTH-WG] Client cannot specify the token type it needs
> 
> Although token type is extensible according to the OAuth core 
> specification - it is fully governed by the Authorization Server.
> 
> There can be a case where a single AS supports multiple token types 
> based on client request.
> 
> But currently we don't have a way the client can specify (or at 
> least suggest) which token type it needs in the OAuth access token 
request ?
> 
> Is this behavior intentional ? or am I missing something...
> 
> Thanks & Regards,
> Prabath
> 
> Mobile : +94 71 809 6732 
> 
> http://blog.facilelogin.com
> http://RampartFAQ.com
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth