[OAUTH-WG] draft-ietf-oauth-pop-key-distribution

Mészáros Mihály <misi@niif.hu> Fri, 03 February 2017 14:54 UTC

To: draft-ietf-oauth-pop-key-distribution@tools.ietf.org, oauth@ietf.org
From: Mészáros Mihály <misi@niif.hu>
Message-ID: <3e63d207-409a-21b7-decd-fcf60f693038@niif.hu>
Date: Fri, 03 Feb 2017 15:53:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------9C0E438C963D7244AE8414D1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/wrrf3p9NahxV0h6v3xVa3rlyA5U>
Subject: [OAUTH-WG] draft-ietf-oauth-pop-key-distribution
Precedence: list

Hi,

Your draft says in
https://tools.ietf.org/html/draft-ietf-oauth-pop-key-distribution-02#section-4.2

	The 'key' parameter either contains a plain JWK structure or a JWK encrypted with a JWE.

But not mentioning that plain JWK is base64url encoded.

In the same section in the example in Figure2:

	 "key":"eyJhbGciOiJSU0ExXzUi 

That is == base64 encoded '{"alg":"RSA1_5'

So "key" is not a plain JWK JSON, but base64 encoded (plain JWK).


So it is confusing for me..

Please confirm that it is missed to state in the draft but you meant
that the plain JWK is in base64 encoded format.

The 'key' parameter either contains a plain _/bas64url encoded/_ JWK structure or a JWK encrypted with a JWE.

Many Thanks,
Misi

[OAUTH-WG] draft-ietf-oauth-pop-key-distribution Mészáros Mihály