[OAUTH-WG] Access token response in application/jwt format

Sergey Beryozkin <sberyozkin@gmail.com> Mon, 01 December 2014 11:09 UTC

Message-ID: <547C4C60.50008@gmail.com>
Date: Mon, 01 Dec 2014 11:09:20 +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: <20141201024133.16302.20230.idtracker@ietfa.amsl.com> <547C495F.1010402@gmail.com>
In-Reply-To: <547C495F.1010402@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/MWjPUnRpo7jWbMumnP6KMmUr370
Subject: [OAUTH-WG] Access token response in application/jwt format
Precedence: list

Hi

OIDC UserInfo endpoint supports returning UserInfo directly in JSON or 
JWS and/or JWE encoded. It is not only useful for OIDC RP clients but 
also allows for supporting a proper HTTP content negotiation, example, 
the implementation of OIDC UserInfo endpoint has a better choice of 
where an optional JWE/JWS encoding can be done, directly in the code or 
via the filters reacting to HTTP Accept.

IMHO it would be good to get it supported directly in OAuth2 token 
responses too. Among other thing it would also help with making the 
whole JOSE effort more popular.

Just an idea, I do not expect any action from the group, but hopefully 
it will be reviewed over time
Sergey

[OAUTH-WG] I-D Action: draft-ietf-oauth-introspec… internet-drafts
Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-intro… Sergey Beryozkin
Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-intro… Sergey Beryozkin
[OAUTH-WG] Access token response in application/j… Sergey Beryozkin
Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-intro… Justin Richer