Re: [OAUTH-WG] New Version Notification for draft-lodderstedt-oauth-jwt-introspection-response-00.txt

Torsten Lodderstedt <torsten@lodderstedt.net> Mon, 19 March 2018 10:17 UTC

Return-Path: <torsten@lodderstedt.net>
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 C0DC7126CE8 for <oauth@ietfa.amsl.com>; Mon, 19 Mar 2018 03:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.493
X-Spam-Level:
X-Spam-Status: No, score=0.493 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L5=3.082, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 SKgpE5-Pw5NI for <oauth@ietfa.amsl.com>; Mon, 19 Mar 2018 03:17:03 -0700 (PDT)
Received: from smtprelay08.ispgateway.de (smtprelay08.ispgateway.de [134.119.228.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30977124BFA for <oauth@ietf.org>; Mon, 19 Mar 2018 03:17:03 -0700 (PDT)
Received: from [80.187.102.250] (helo=[172.20.10.2]) by smtprelay08.ispgateway.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from <torsten@lodderstedt.net>) id 1exrqp-00050c-Io; Mon, 19 Mar 2018 11:17:11 +0100
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Message-Id: <D5EA9141-08A3-427A-A4E7-A69DD5138327@lodderstedt.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_FCD637DE-13B8-4F9F-873D-88D002DF4819"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 19 Mar 2018 11:16:58 +0100
In-Reply-To: <85274C99-A8AA-452C-B8BC-46E7869642EB@oracle.com>
Cc: LARMIGNAT Louis <Louis.LARMIGNAT@wavestone.com>, Brock Allen <brockallen@gmail.com>, "oauth@ietf.org" <oauth@ietf.org>
To: Phil Hunt <phil.hunt@oracle.com>
References: <152140077785.15835.11388192447917251931.idtracker@ietfa.amsl.com> <2A1E98B8-973E-44F0-96F0-E319FD6969A8@lodderstedt.net> <308c1c61-a2ba-4e45-9fe6-9d525e554fb7@getmailbird.com> <DB5PR03MB1191DFA3BACC2806E2C07899F6D40@DB5PR03MB1191.eurprd03.prod.outlook.com> <85274C99-A8AA-452C-B8BC-46E7869642EB@oracle.com>
X-Mailer: Apple Mail (2.3445.5.20)
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC5uZXQ=
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/gXMlophDX6lE20cUjSxI2kFh7xk>
Subject: Re: [OAUTH-WG] New Version Notification for draft-lodderstedt-oauth-jwt-introspection-response-00.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Mar 2018 10:17:06 -0000

We explicitly want the token (JSON object) to be signed not the HTTP response. I think using JWS is the most generic way to achieve that goal.

> Am 19.03.2018 um 09:57 schrieb Phil Hunt <phil.hunt@oracle.com>:
> 
> This draft has similar issues to https://tools.ietf.org/html/draft-richer-oauth-signed-http-request-01 <https://tools.ietf.org/html/draft-richer-oauth-signed-http-request-01>
> 
> Rather than *try* sign HTTP, a signed JWT object is more reliably returned.
> 
> Phil
> 
> 
>> On Mar 19, 2018, at 8:25 AM, LARMIGNAT Louis <Louis.LARMIGNAT@wavestone.com <mailto:Louis.LARMIGNAT@wavestone.com>> wrote:
>> 
>> Hi,
>>  
>> The draft Signing HTTP Messages <> (https://tools.ietf.org/html/draft-cavage-http-signatures-09 <https://tools.ietf.org/html/draft-cavage-http-signatures-09>) could not meet this requirement in a more generic way ?
>>  
>> Regards,
>> Louis
>>  
>> De : OAuth <oauth-bounces@ietf.org <mailto:oauth-bounces@ietf.org>> De la part de Brock Allen
>> Envoyé : dimanche 18 mars 2018 20:40
>> À : Torsten Lodderstedt <torsten@lodderstedt.net <mailto:torsten@lodderstedt.net>>; oauth@ietf.org <mailto:oauth@ietf.org>
>> Objet : Re: [OAUTH-WG] Fwd: New Version Notification for draft-lodderstedt-oauth-jwt-introspection-response-00.txt
>>  
>> Why is TLS to the intospection endpoint not sufficient? Are you thinking there needs to be some multi-tenancy support of some kind?
>>  
>> -Brock
>>  
>> On 3/18/2018 3:33:16 PM, Torsten Lodderstedt <torsten@lodderstedt.net <mailto:torsten@lodderstedt.net>> wrote:
>> 
>> Hi all,
>>  
>> I just submitted a new draft that Vladimir Dzhuvinov and I have written. It proposes a JWT-based response type for Token Introspection. The objective is to provide resource servers with signed tokens in case they need cryptographic evidence that the AS created the token (e.g. for liability). 
>>  
>> I will present the new draft in the session on Wednesday.
>>  
>> kind regards,
>> Torsten. 
>> 
>> 
>> Anfang der weitergeleiteten Nachricht:
>>  
>> Von: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>> Betreff: New Version Notification for draft-lodderstedt-oauth-jwt-introspection-response-00.txt
>> Datum: 18. März 2018 um 20:19:37 MEZ
>> An: "Vladimir Dzhuvinov" <vladimir@connect2id.com <mailto:vladimir@connect2id.com>>, "Torsten Lodderstedt" <torsten@lodderstedt.net <mailto:torsten@lodderstedt.net>>
>>  
>> 
>> A new version of I-D, draft-lodderstedt-oauth-jwt-introspection-response-00.txt
>> has been successfully submitted by Torsten Lodderstedt and posted to the
>> IETF repository.
>> 
>> Name:           draft-lodderstedt-oauth-jwt-introspection-response
>> Revision: 00
>> Title:          JWT Response for OAuth Token Introspection
>> Document date:  2018-03-15
>> Group:          Individual Submission
>> Pages:          5
>> URL:            https://www.ietf.org/internet-drafts/draft-lodderstedt-oauth-jwt-introspection-response-00.txt <https://www.ietf.org/internet-drafts/draft-lodderstedt-oauth-jwt-introspection-response-00.txt>
>> Status:         https://datatracker.ietf.org/doc/draft-lodderstedt-oauth-jwt-introspection-response/ <https://datatracker.ietf.org/doc/draft-lodderstedt-oauth-jwt-introspection-response/>
>> Htmlized:       https://tools.ietf.org/html/draft-lodderstedt-oauth-jwt-introspection-response-00 <https://tools.ietf.org/html/draft-lodderstedt-oauth-jwt-introspection-response-00>
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-lodderstedt-oauth-jwt-introspection-response <https://datatracker..ietf.org/doc/html/draft-lodderstedt-oauth-jwt-introspection-response>
>> 
>> 
>> Abstract:
>>   This draft proposes an additional JSON Web Token (JWT) based response
>>   for OAuth 2.0 Token Introspection.
>> 
>> 
>> 
>> 
>> 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 <http://tools.ietf.org/>.
>> 
>> The IETF Secretariat
>> 
>>  
>> The information transmitted in the present email including the attachment is intended only for the person to whom or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete all copies of the material. 
>> 
>> Ce message et toutes les pièces qui y sont éventuellement jointes sont confidentiels et transmis à l'intention exclusive de son destinataire. Toute modification, édition, utilisation ou diffusion par toute personne ou entité autre que le destinataire est interdite. Si vous avez reçu ce message par erreur, nous vous remercions de nous en informer immédiatement et de le supprimer ainsi que les pièces qui y sont éventuellement jointes. _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org <mailto:OAuth@ietf.org>
>> https://www.ietf.org/mailman/listinfo/oauth <https://www.ietf.org/mailman/listinfo/oauth>
>