feat: add custom audience support to user JWT builder#2717
Merged
Conversation
Add WithAudience functional option to allow generating JWT tokens with custom audience claims. This enables separate validation paths for different token types (e.g., MCP user tokens) while maintaining backward compatibility with the default audience. Signed-off-by: Miguel Martinez <miguel@chainloop.dev>
javirln
approved these changes
Feb 9, 2026
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
2 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.
Add WithAudience functional option to allow generating JWT tokens with custom audience claims. This enables separate validation paths for different token types (e.g., MCP user tokens) while maintaining backward compatibility with the default audience.
Also updates license headers to 2023-2026 and clarifies the CLAUDE.md license header rule for 2026.