IETF Logo Mail Archive

[OAUTH-WG] Code and token response thumbprints ?

Sergey Beryozkin <sberyozkin@gmail.com> Wed, 05 November 2014 10:20 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 23F961A8854 for <oauth@ietfa.amsl.com>; Wed, 5 Nov 2014 02:20:23 -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 QtQQ-6zROYIA for <oauth@ietfa.amsl.com>; Wed, 5 Nov 2014 02:20:21 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BCF01A8853 for <oauth@ietf.org>; Wed, 5 Nov 2014 02:20:21 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id 10so358428lbg.21 for <oauth@ietf.org>; Wed, 05 Nov 2014 02:20:19 -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=LDgZLi/LmLCuOLeelU87+UWGnX4f98JUmQDlHuTewu4=; b=falOqe/WVJAoM3+T+tWKksU8wEPCaTrtZlsu6RE34O8aYUFt3KNnWvWr9C9Jd2HslE d4n6H2hrrI9txFwVTH1Vo0HiPsx2PM+v+AjVvWAzM8bvBXuBAYCW6JSZmVgFdd25OkRj v1BU4czC2+HbfOtvqF7YOZNelObU+pn9YA+KQ8ee6RrbVXKvrO6p24dWWiA5wQ2/fZne tRQ3f+x1xp2PlUdTXNw4fvvHXutMuFzHG8Wpv8/6d7A7WqTpqsS+nA9W30MZL3QYQlrx hE56YC2MR5wpG4sdf0uM8RUkNASNaZpHOZBuVF7XUxPgs10sLFidejIztw7ZpZWR7f3q HuAg==
X-Received: by 10.153.7.107 with SMTP id db11mr66878784lad.35.1415182819517; Wed, 05 Nov 2014 02:20:19 -0800 (PST)
Received: from [10.36.226.2] ([80.169.137.63]) by mx.google.com with ESMTPSA id q7sm1151742laq.32.2014.11.05.02.20.17 for <oauth@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Nov 2014 02:20:18 -0800 (PST)
Message-ID: <5459F9D5.4000405@gmail.com>
Date: Wed, 05 Nov 2014 10:20:05 +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: <545760D7.3090900@surfnet.nl> <CAOyugYZnEz-uhA9M-1bx1m9cVf0UG8cH7aB+-skHiKmwh0Aikg@mail.gmail.com> <0FBFB9F2-508B-495B-9075-E664351C8D96@mitre.org>
In-Reply-To: <0FBFB9F2-508B-495B-9075-E664351C8D96@mitre.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/Q7x4m5E5uQef_ab2JDet46F8Apc
Subject: [OAUTH-WG] Code and token response thumbprints ?
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: Wed, 05 Nov 2014 10:20:23 -0000

Hi

Code and access token hashes that can be returned in OIDC responses is a 
good idea. I wonder, does it make any sense to have something like that 
supported at the 'bare' OAuth2 level alone to lower the complexity level 
(example, dealing with JWS id_tokens containing an access token hash may 
not be trivial) and just make this OIDC a_hash/c_hash idea generalized ?

For example, a JWK thumbprint [1] idea can be adapted.
Suppose the following is returned to the Client:
{"access_token":"123456", "refresh_token":"654321"}.

The approach at [1] can be applied producing:

{"access_token":"123456", "refresh_token":"654321", 
"thumbprint":"AxTh-Rtyw"}.

Similarly for code responses...

Just an idea...

Sergey

[1] 
http://tools.ietf.org/html/draft-jones-jose-jwk-thumbprint-00#section-3.3

v2.23.0 | Report a Bug | By Email