Re: [OAUTH-WG] Client cannot specify the token type it needs
zhou.sujing@zte.com.cn Mon, 21 January 2013 05:39 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 065A721F881E for <oauth@ietfa.amsl.com>; Sun, 20 Jan 2013 21:39:11 -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 x0Lj8-tiKdoC for <oauth@ietfa.amsl.com>; Sun, 20 Jan 2013 21:39:10 -0800 (PST)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id CC7A721F881C for <oauth@ietf.org>; Sun, 20 Jan 2013 21:39:01 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id A2A81126200E; Mon, 21 Jan 2013 13:41:35 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id ABDDEDF5343; Mon, 21 Jan 2013 13:42:41 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id r0L5cf0u003105; Mon, 21 Jan 2013 13:38:41 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <CAJV9qO-D=9-Dbi8Rp8fdXYSYOMeNhfVbSmk2_u3z=Vy3tiyzLw@mail.gmail.com>
To: Prabath Siriwardena <prabath@wso2.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF0057633A.B16D5C4E-ON48257AFA.001EACB5-48257AFA.001F07AC@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Mon, 21 Jan 2013 13:38:41 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-01-21 13:38:44, Serialize complete at 2013-01-21 13:38:44
Content-Type: multipart/alternative; boundary="=_alternative 001F07AC48257AFA_="
X-MAIL: mse02.zte.com.cn r0L5cf0u003105
Cc: "oauth@ietf.org WG" <oauth@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:39:11 -0000
Well, if RS could specify token type, then Client could transfer it to AS, I think, but it is not a good idea for client itself to specify the token type. Prabath Siriwardena <prabath@wso2.com> 写于 2013-01-21 13:29:05: > Think about a distributed setup. You have single Authorization > Server and multiple Resource Servers. > > Although OAuth nicely decouples AS from RS - AFAIK there is no > standard established for communication betweens AS and RS - how to > declare metadata between those. > > Also there can be Resource Servers which support multiple token > types. It could vary on APIs hosted in a given RS. > > Thanks & regards, > -Prabath > > On Mon, Jan 21, 2013 at 10:48 AM, <zhou.sujing@zte.com.cn> wrote: > > 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 tokenrequest ? > > > > 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 > > > -- > Thanks & Regards, > Prabath > > Mobile : +94 71 809 6732 > > http://blog.facilelogin.com > http://RampartFAQ.com
- [OAUTH-WG] Client cannot specify the token type i… Prabath Siriwardena
- Re: [OAUTH-WG] Client cannot specify the token ty… William Mills
- Re: [OAUTH-WG] Client cannot specify the token ty… zhou.sujing
- Re: [OAUTH-WG] Client cannot specify the token ty… Prabath Siriwardena
- Re: [OAUTH-WG] Client cannot specify the token ty… zhou.sujing
- Re: [OAUTH-WG] Client cannot specify the token ty… William Mills
- Re: [OAUTH-WG] Client cannot specify the token ty… zhou.sujing
- Re: [OAUTH-WG] Client cannot specify the token ty… Prabath Siriwardena
- Re: [OAUTH-WG] Client cannot specify the token ty… zhou.sujing
- Re: [OAUTH-WG] Client cannot specify the token ty… Prabath Siriwardena
- Re: [OAUTH-WG] Client cannot specify the token ty… Eve Maler
- Re: [OAUTH-WG] Client cannot specify the token ty… George Fletcher
- Re: [OAUTH-WG] Client cannot specify the token ty… Eve Maler