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.
Description
Add support for the
azp
(Authorized Party) claim in JWT token client ID extraction to improve compatibility with OpenID Connect standard implementations.Problem: The current JWT verifier only checks
client_id
andsub
claims when extracting the client identifier from JWT tokens. However, many identity providers (including Keycloak, Auth0, and other enterprise OIDC implementations) use theazp
claim to represent the client application ID, as defined in the OpenID Connect Core 1.0 specification.Solution: Extended the client ID extraction fallback chain to include the
azp
claim:This change maintains full backwards compatibility while supporting standard OIDC implementations that rely on the
azp
claim for client identification.Contributors Checklist
Review Checklist
Note: You'll need to create an issue first describing this enhancement before submitting the PR, and then update the issue number in the checklist above.