access_token: allow handling the /userinfo as a JWT token #107
+28
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Though user information is usually returned as plain JSON, the spec does allow a JWT as well[1]: > The UserInfo Claims MUST be returned as the members of a JSON object unless a signed or encrypted response was requested during Client Registration. I'm working with a provider that only returns JWT and does not allow Content-Type override. The workaround is to check the response's content type and parse the JWT if relevant. [1]: https://openid.net/specs/openid-connect-core-1_0.html#UserInfo
Author
|
Sorry I did not see #106 🤦 |
freesteph
added a commit
to betagouv/standards-front
that referenced
this pull request
Apr 30, 2025
Until nov/openid_connect#107 hopefully gets merged.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Though user information is usually returned as plain JSON, the spec does allow a JWT as well1:
I'm working with a provider that only returns JWT and does not allow Content-Type override. The workaround is to check the response's content type and parse the JWT if relevant.