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

Standalone and documented claims api #626

Merged
merged 3 commits into from
Oct 2, 2024
Merged

Conversation

anakinj
Copy link
Member

@anakinj anakinj commented Oct 2, 2024

Description

This is the beginning of officially supporting a JWT token claims api.

Checklist

Before the PR can be merged be sure the following are checked:

  • There are tests for the fix or feature added/changed
  • A description of the changes and a reference to the PR has been added to CHANGELOG.md. More details in the CONTRIBUTING.md

@anakinj anakinj force-pushed the official-claims-api branch 2 times, most recently from fbe539f to e9944f3 Compare October 2, 2024 18:49
@anakinj anakinj force-pushed the official-claims-api branch 2 times, most recently from 8627616 to 279355d Compare October 2, 2024 18:54
@anakinj anakinj force-pushed the official-claims-api branch 7 times, most recently from 1ee202e to fe5d51e Compare October 2, 2024 20:27
@anakinj anakinj merged commit 5144e6a into jwt:main Oct 2, 2024
34 checks passed
nevans added a commit to nevans/omniauth-google-oauth2 that referenced this pull request Oct 3, 2024
This is a continuation of zquestz#464, which fixed backward compatibility with
jwt v2.9.0 and v2.9.1.  v2.9.2 brought back the removed APIs, for
backward compatibility, but marked them as internal only and/or
deprecated.

For context, see the discussion here:
* jwt/ruby-jwt#623
* jwt/ruby-jwt#626
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant