[Openid-specs-ab] "reg" claim in JWT

Nat Sakimura sakimura at gmail.com
Tue Dec 11 01:33:02 UTC 2012


As it was discussed during today's call, here is the concrete proposal that
I am making.

I would take them to OAuth ML if you guys agree.


There are two types: Brief one, and more specified one.

*(Option 1) Really brief one*

4.1.9. "reg" (Registered to) Claim
The "reg" (registered to) claim is the Client ID of the user of the
JWT that the audience is able to identify the client with. This claim
is OPTIONAL.


*(Option 2) Brief one*

Add the following to the JWT.

4.1.9. "reg" (Registered to) Claim
The "reg" (registered to) claim identifies the client that the JWT is
intended for. The client intended to use the JWT MUST be identified by
the audience with the value of this claim.
The "reg" value is a case sensitive string containing a StringOrURI
value.This claim is OPTIONAL. If the principal processing the claim
does not identify the user of the JWT with the identifier in the "reg"
claim value, then the JWT MUST be rejected. The interpretation of the
registered to value is generally application specific.

*
*

*(Option 3) More specified one*

Add the following to the JWT.

4.1.9. "reg" (Registered to) Claim
The "reg" (registered to) claim identifies the client that the JWT is
intended for. The client intended to use the JWT MUST be identified by
the audience with the value of this claim.
The "reg" value is a case sensitive string containing a StringOrURI
value.This claim is OPTIONAL. If the principal processing the claim
does not identify the user of the JWT with the identifier in the "reg"
claim value, then the JWT MUST be rejected. The interpretation of the
registered to value is generally application specific.
A typical example of a registered to claim includes following: * A
base64url encoded JWK. * A base64url encoded DER. * A URL that points
to the key material that the audience can use to
  authenticate the user of the JWT. * client_id that the audience can
use to authenticate and
  identify the client.

4.1.10 "rct" (Registered to claim type)
The "rct" (Registered to claim type) identifies the type of the "reg"
claim. It is a StringOrURI value. The defined values are the
following:

"jwk" The value of the "reg" claim is a base64url encoded JWK of the
registered client.

"x5u" The value of the "reg" claim is the URL that points to the
public key certificate of the registered client. The format of the
content that x5u points to is described in section 4.1.4 of the JSON
Web Signature.

"client_id" The value of the "reg" claim is the Client ID of the
client that the audience of the JWT is able to use to authenticate the
client.

Alternatively, they can be added to Table 1 of the Messages, but I think it
is general enough that it should live in JWT.

-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20121211/013df1b5/attachment-0001.html>


More information about the Openid-specs-ab mailing list