-
Notifications
You must be signed in to change notification settings - Fork 785
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
Using integers for registered date claims is deprecated, please use DateTimeImmutable objects instead. #1381
Comments
https://github.com/lcobucci/jwt/blob/3.4.0/src/Builder.php update 9 hours ago
In your project composer.json add "lcobucci/jwt": "3.3.3" and execute composer update. |
Can confirm that this is because "lcobucci/jwt" upgraded to 3.4 with a lot of breaking changes. Downgrading this to 3.3.3 fixes the issue. |
Sorry @Linij do not understand your comment. Also seeing this a few minutes ago.
|
In your project composer.json add "lcobucci/jwt": "3.3.3" and execute composer update. @andrewmclagan |
@Linij That solved the issue. Thank you! What downstream packages requires this? |
Ok, |
These errors shouldn't be showing on production. If you have these turned on, update your php.ini file to change the error level 👍 |
Was caught in CI long before prod. |
It won't be a problem in prod if you have these errors suppressed. If your CI is for prod it should probably be suppressed in that build env too |
@andrewmclagan Also an instruction |
there seems to be multiple different problems with |
This is a deprecation notice and these shouldn't be enabled on production. |
I want to investigate something: is this exception thrown with |
I've discovered that these exceptions are handled a little differently in Laravel. I'll try to investigate that more thoroughly in the upcoming days/weeks. In the meantime please stick onto |
TIL about |
I've just released v10.1.0 with support for OAuth2 Server v8.2.0 and JWT v3.4.0/v4.0.0 that should fix these issues. Please update 🙂 |
Lol what a timing, ran into this issue 10 minutes ago. Thanks @driesvints :-) |
@driesvints will there also be a patch for version 9? Laravel 6 still has support for about a year, and it can't use passport>9 |
I added "lcobucci/jwt": "3.3.3" to my project and it worked, thank you! |
I upgraded Passport to 10.1.0 and it worked, thanks guys. |
I've just released v9.4.0 which supports PHP 8 |
All Possible Solution Added here Replicating claims as headers is deprecated and will removed from v4.0 – Laravel Passport Problem in lcobucci/jwt package |
This is a fix of an error raised when calling $user()->createToken(). See the following for further details on the bug and fix: - laravel/passport#1381 - https://stackoverflow.com/questions/65017721/laravel-passport-target-lcobucci-jwt-parser-is-not-instantiable-while-buildin
just add In composer.json "lcobucci/jwt": "3.3.3" and execute composer update. |
Description:
This Error Appears
Steps To Reproduce:
after tracing error : I found that passport package depends on
lcobucci/jwt
that made major update in these classeslcobucci/jwt/src/Signer/BaseSigner.php
The text was updated successfully, but these errors were encountered: