Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-01.txt

Sergey Beryozkin <sberyozkin@gmail.com> Thu, 27 November 2014 17:55 UTC

Return-Path: <sberyozkin@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BB61A00B9 for <oauth@ietfa.amsl.com>; Thu, 27 Nov 2014 09:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5GVUDSyjHYO1 for <oauth@ietfa.amsl.com>; Thu, 27 Nov 2014 09:55:32 -0800 (PST)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16FA11A00A3 for <oauth@ietf.org>; Thu, 27 Nov 2014 09:55:32 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id bs8so16454135wib.10 for <oauth@ietf.org>; Thu, 27 Nov 2014 09:55:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ZAiaW/WiRx+7NPHCS3vYOnLJg4lcH6iWWdSBnwjQs7Q=; b=wqdrugD5peIR8TVZLGrpLQGRFjto6IK7zlOEhbT3LwXENbQY3f2IIkE1Gl3ecqnhua 1a/mQHi69nDEYTBwD41/YnBTdFUE+X4sYmZFtSjPCAf+gtQaUXASkxJ4vcENMmbzuvMs zx5tzqu8g4hPfr+YmgbrA/AH2tL0i+QJVA+7+1G1PO5OMY2nQ1/8yGHsq/28/WC4u6bs Lu/pYIr8u0ieyQeoaPVIpjcL4zshPLPmDo8+sK/4jyGs0XVfTWmHlbTXPkmdr7z9IDWF Ub48sq+tFJsM9eYlWp5882onNA6HtoDV1PLkKjmT6YuL4unKO2ruoUW+gsDxMnuQyCus 7myA==
X-Received: by 10.180.96.10 with SMTP id do10mr54109340wib.16.1417110930835; Thu, 27 Nov 2014 09:55:30 -0800 (PST)
Received: from [192.168.2.7] ([109.255.82.67]) by mx.google.com with ESMTPSA id e7sm11662376wjx.31.2014.11.27.09.55.28 for <oauth@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Nov 2014 09:55:30 -0800 (PST)
Message-ID: <5477657D.6040302@gmail.com>
Date: Thu, 27 Nov 2014 17:55:09 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: oauth@ietf.org
References: <20141113040729.675.60416.idtracker@ietfa.amsl.com>
In-Reply-To: <20141113040729.675.60416.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/jMNT_h0WfOM_XIapNyC6rSF3v_I
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-01.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 27 Nov 2014 17:55:34 -0000

Hi

Should the text require that a "client_id" parameter is always included 
as a query parameter too ?

If it is only inside a 'request' parameter then how the server would 
identify a client specific key that can be used to validate the signature ?

Or is the idea that if it is JWS and no client_id query parameter is 
available then a client id is extracted first, the key is identified and 
then the signature is validated ?

Also, a simple example how an optional file hash is specified when a 
request_uri is used would be useful

Many thanks, Sergey
On 13/11/14 04:07, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Web Authorization Protocol Working Group of the IETF.
>
>          Title           : Request by JWS ver.1.0 for OAuth 2.0
>          Authors         : Nat Sakimura
>                            John Bradley
> 	Filename        : draft-ietf-oauth-jwsreq-01.txt
> 	Pages           : 9
> 	Date            : 2014-11-12
>
> Abstract:
>     The authorization request in OAuth 2.0 utilizes query parameter
>     serialization.  This specification defines the authorization request
>     using JWT serialization.  The request is sent through "request"
>     parameter or by reference through "request_uri" parameter that points
>     to the JWT, allowing the request to be optionally signed and
>     encrypted.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-oauth-jwsreq-01
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-jwsreq-01
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>