Bug in the JWT implementation | ww.wp.xz.cn

Resolved sviluppomania
(@sviluppomania)

1 year, 1 month ago

Hi, there is currently a bug in the JWT implementation that does not consider either solar time or daylight saving time. It is necessary to add a lag on the validity of the 1 hour token: open the file .\ .\wp-content\plugins\google-site-kit\third-party\firebase\php-jwt\src\JWT.php and assign the static variable $leeway the value 3600 (if it activates solar time) or 7200 (if it activates daylight saving time). Hoping for your Debug of this implementation. Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)

Plugin Support James Osborne
(@jamesosborne)

1 year, 1 month ago

Thanks for getting in touch @sviluppomania. I’ll check this with the team and report back to you here. It may be later in the week before I have any update, but I’ll let you know as soon as possible. Thank you.

Thread Starter sviluppomania
(@sviluppomania)

1 year, 1 month ago

@jamesosborne For more details on the issue, you can check out our answer here: https://ww.wp.xz.cn/support/topic/bug-in-the-jwt-implementation/#post-18432663

Do you have any updates on this? Thanks.

Plugin Support James Osborne
(@jamesosborne)

1 year, 1 month ago

I don’t have any update just yet @sviluppomania, but I will today or tomorrow. Thanks for the additional details.

Plugin Author Evan Mattson
(@aaemnnosttv)

1 year, 1 month ago

Hi @sviluppomania , thanks for raising this. The code you’re referring to is part of an external library (https://github.com/firebase/php-jwt). Please raise this with the maintainers to address this issue both in Site Kit and for everyone else who uses it.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Bug in the JWT implementation’ is closed to new replies.

4 replies
3 participants
Last reply from: Evan Mattson
Last activity: 1 year, 1 month ago
Status: resolved