recommendation to the use of explicit typing for ID Tokens

[bitbucket-import-issues]

Originally submitted by Andrii Deinega (Andrii Deinega) on 2024-07-29

The OpenID Connect Core 1.0 incorporating (errata set 2) neither defines a value for the “typ” header parameter nor requires the use of it (see section the explicit typing in RFC 8725 JSON Web Token Best Current Practices).

The suggestion is at least to recommend using it for 1.0.

Newer versions of the spec can require it, the same holds true for Logout Tokens

It is RECOMMENDED that Logout Tokens be explicitly typed. This is accomplished by including a typ (type) Header Parameter with a value of logout+jwt in the Logout Token.

and for JWT assertions that are used as client credentials (client_secret_jwt and private_key_jwt).

---

Bitbucket status: open

Bitbucket origin: issue 2162

[bitbucket-import-issues]

Originally submitted by Andrii Deinega (Andrii Deinega) on 2024-07-29

Among many other things, this is a defensive mechanism against the misuse for a family of use cases where ID Tokens get exchanged for something else (using the token exchange grant type) especially in cases where an authorization server performing an exchange doesn’t belong to the security domain which issued an ID Token.

[bitbucket-import-issues]

Originally submitted by mbj (Michael Jones) on 2024-07-30

We discussed this on the 29-Jul-24 working group call. We agreed that this would be something to do in a next version.

Brian Campbell also cited anecdotal evidence of deployments using explicit typing in some contexts causing code failures.

[bitbucket-import-issues]

Originally submitted by Brian Campbell (Brian Campbell) on 2024-07-30

some pointers to discussion around the anecdotal failures:

https://bitbucket.org/openid/fapi/issues/684/typ-in-request-objects

https://bitbucket.org/openid/fapi/pull-requests/493

https://bitbucket.org/openid/fapi/issues/705/conformance-testing-for-typ-in-request