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.

Sign up for GitHub

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

Jump to bottom

fix: broken JSON round-tripping for custom claims #3819

Merged
merged 2 commits into from
Aug 14, 2024
Merged

fix: broken JSON round-tripping for custom claims #3819

merged 2 commits into from
Aug 14, 2024

Commits on Aug 12, 2024

  1. fix: incorrect context passthru

    @alnr
    alnr committed Aug 12, 2024
    Configuration menu
    Copy the full SHA
    23c7464 View commit details
    Browse the repository at this point in the history

Commits on Aug 13, 2024

  1. fix: broken JSON round-tripping for custom claims 

    Adding custom claims with numerical types (think JavaScript Number) previously did not
round-trip through Hydra correctly. For example, passing UNIX timestamps in custom claims
would end up as floating points in exponential notation in the final token. That, in turn,
confused or broke downstream consumers of the token, including Kratos.

Ref go-jose/go-jose#144
    @alnr
    alnr committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    a28aed9 View commit details
    Browse the repository at this point in the history