feat: add issuer claim and RFC 8414 metadata endpoint#2
Merged
Conversation
wolf4ood
approved these changes
Jun 5, 2026
jimmarino
approved these changes
Jun 5, 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
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.
Summary
issclaim identifying jwtlet as the authorization server (previously empty). The issuer is jwtlet itself, not the subject token's original issuer (which remains inact.iss) and not Vault, whose transit engine is only the signing primitive.issuerconfig value (required, must be a valid URL), wired intoTokenExchangeServiceand validated at startup.GET /.well-known/oauth-authorization-serveron the token-exchange port (default 8080), advertisingissuer,token_endpoint,jwks_uri,grant_types_supported, andtoken_endpoint_auth_methods_supported.Changes
jwtlet-core:TokenExchangeServicegains anissuerfield; issuedTokenClaimsnow setiss.jwtlet-server: newmetamodule withAuthorizationServerMetadata+ handler; route registered on the exchange API;issueradded to config with validation; assembly/main wiring.issueradded tojwtlet-config.yaml.metadata.rsverifying the metadata document contents and the JWKS endpoint.