Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: add support for multiple jwks keys per endpoint #753

Merged
merged 6 commits into from
Feb 7, 2025

Conversation

jairad26
Copy link
Contributor

@jairad26 jairad26 commented Feb 7, 2025

Description

This change allows for multiple keys per jwks endpoint, where previously it only used the first key in the endpoint.

Checklist

All PRs should check the following boxes:

  • I have given this PR a title using the
    Conventional Commits syntax, leading with fix:,
    feat:, chore:, ci:, etc.
    • The title should also be used for the commit message when the PR is squashed and merged.
  • I have formatted and linted my code with Trunk, per the instructions in
    the contributing guide.

If the PR includes a code change, then also check the following boxes. (If not, then delete the
next section.)

  • I have added an entry to the CHANGELOG.md file.
    • Add to the "UNRELEASED" section at the top of the file, creating one if it doesn't yet exist.
    • Be sure to include the link to this PR, and please sort the section numerically by PR number.
  • I have manually tested the new or modified code, and it appears to behave correctly.
  • I have added or updated unit tests where appropriate, if applicable.

@jairad26 jairad26 requested a review from a team as a code owner February 7, 2025 07:35
@jairad26 jairad26 enabled auto-merge (squash) February 7, 2025 16:44
@jairad26 jairad26 merged commit 1a17c24 into main Feb 7, 2025
54 checks passed
@jairad26 jairad26 deleted the jai/hyp-2901-support-multiple-keys-in-jwks branch February 7, 2025 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants