chore: Jwt migration to the monorepo - #9690
Open
Hectorhammett wants to merge 323 commits into
Open
Hectorhammett wants to merge 323 commits into
Hectorhammett wants to merge 323 commits into
Conversation
…ctor Refactor decode() code path to address security vulnerabilities
…tests Add a few add'l tests - more forthcoming
target-dir was meant to allow using the root of the package as a PSR-4 root and make composer prepend the target dir when installing to make it compatible with PSR-0, before PSR-4 was a reality. This setting is deprecated in Composer in favor of using PSR-4, and it is not needed anyway when using the classmap autoloading.
Remove the useless target-dir setting from the composer config
Provide a leeway in verification of times to account for clock skew
Allow using \ArrayAccess as $key in \JWT::decode
…t-isolation Reset clock skew / leeway after relevant tests & update README
…leapis/php-jwt#634) * fix: validate numeric type of iat, nbf and exp claims in encode The decode() path already rejected non-numeric iat/nbf/exp values, but encode() accepted any type and silently produced an invalid token. Add the same is_numeric guards in encode() and cover them with unit tests. Signed-off-by: Guillaume Delré <delre.guillaume@gmail.com> * test: add regression test for numeric string timestamps in encode Covers the case where iat/nbf/exp are passed as numeric strings (e.g. (string) time()), which must remain accepted to avoid a breaking change. Signed-off-by: Guillaume Delré <delre.guillaume@gmail.com> --------- Signed-off-by: Guillaume Delré <delre.guillaume@gmail.com> Co-authored-by: Brent Shaffer <betterbrent@google.com>
Avoid redirection: - From: https://github.com/firebase/php-jwt - To: https://github.com/googleapis/php-jwt Co-authored-by: Brent Shaffer <betterbrent@google.com>
…ase--branches--main chore(main): release 7.1.1
Hectorhammett
added
the
do not merge
Hectorhammett
force-pushed
the
jwt-migration
branch
2 times, most recently
from
September 14, 2026 23:33
037a45a to
63098db
Compare
Hectorhammett
force-pushed
the
jwt-migration
branch
3 times, most recently
from
September 15, 2026 21:53
e3414cd to
2af2c23
Compare
Hectorhammett
force-pushed
the
jwt-migration
branch
from
September 15, 2026 23:29
2af2c23 to
9b3818d
Compare
Hectorhammett
marked this pull request as ready for review
September 16, 2026 00:27
Hectorhammett
removed
the
do not merge
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
20 participants
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.
No description provided.