specs says type in header should at+jwt#990
Closed
arthurchan35 wants to merge 1 commit intoapache:mainfrom
Closed
Conversation
Contributor
Author
reta
reviewed
Aug 22, 2022
| getJwtAccessTokenProducer() == null ? new OAuthJoseJwtProducer() : getJwtAccessTokenProducer(); | ||
| return processor.processJwt(new JwtToken(jwtCliams)); | ||
|
|
||
| JwsHeaders jwsHeaders = new JwsHeaders(); |
Member
There was a problem hiding this comment.
@arthurchan35 it does not seem to be solving the problem at large:
- as you may see in the comment [1], it could be JWS or JWE
- for
JWE, theJwsHeadersare not used, theJweHeadersare
Looking into the right place to apply the spec recommendation, but on more general note, we need to introduce a member to JoseType for at+JWT and respective constant to JoseConstants.
Contributor
Author
There was a problem hiding this comment.
Hi @reta, thanks for the review!
According to RFC 9068 sections 2.1 and section 4, a JWT access token must be signed, optionally encrypted. As I interpret the comment, it means the same thing as specs required?
Regarding JoseType and JoseConstants, I will look into them bit more.
gnodet
added a commit
that referenced
this pull request
Mar 11, 2026
Per RFC 9068 Section 2.1, JWT access tokens MUST include a typ header parameter set to "at+jwt". This change: - Adds TYPE_AT_JWT constant to JoseConstants - Adds AT_JWT member to JoseType enum with proper lookup - Sets the at+jwt type on both JWS and JWE headers when producing JWT access tokens in AbstractOAuthDataProvider Closes #990 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3 tasks
Contributor
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
https://datatracker.ietf.org/doc/html/rfc9068#section-2.1