Support JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens

[mooreds]

JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens

Problem

This standardized the JWT format for OAuth access tokens. Our JWTs are not compliant.

Solution

Support the standard. From a readthrough it seems like:

• it'd be a break in compatibility for the typ header in our issued access token JWTs

and that is about it.

Alternatives/workarounds

n/a

Additional context

https://www.rfc-editor.org/rfc/rfc9068.html is the spec

Community guidelines

All issues filed in this repository must abide by the FusionAuth community guidelines.

How to vote

Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.