-
-
Notifications
You must be signed in to change notification settings - Fork 614
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
Remove guard related service definitions when authenticator manager is enabled. #879
Comments
I get this deprecation notice after migrating to the new authentication system:
The deprecation only shows the first time I run my tests (or after running Could it be related to this issue? |
@jzecca I think so, yes. I'm looking at it. |
I still get deprecation message after composer upgrade Remaining indirect deprecation notices (1) 1x: The "Lexik\Bundle\JWTAuthenticationBundle\Security\Guard\JWTTokenAuthenticator" class implements "Symfony\Component\Security\Guard\AuthenticatorInterface" that is deprecated since Symfony 5.3, use the new authenticator system instead. |
Did you also upgrade your security config to use the new authenticator instead of Guard? |
You meant this
? |
Nope, I mean:
As documented and mentioned in https://github.com/lexik/LexikJWTAuthenticationBundle/blob/2.x/UPGRADE-2.12.md. |
Yep. I tried both. Now
and result the same
|
Please create a small application with enough code to reproduce. I can’t reproduce on my side and our functional test suite does not suffer from this issue. |
Most probably you have |
I found it. var/cahe directory was not empty after clearing cache (bin/console cache:clear --env=test) After I manually removed all file and restart tests - deprecations message gone. |
I upgraded to v2.12.2, adapted the security config as mentioned above and get the same deprecation message in a unit test that extends KernelTestCase and does not directly use or test anything related to the JWTAuthenticationBundle. What else can I check or did I miss maybe? |
Please create a small application with enough code to reproduce. I can’t reproduce on my side and our functional test suite does not suffer from this issue. Commenting on closed/merged tickets as it hijacks the discussion. |
Try my case.
|
No description provided.
The text was updated successfully, but these errors were encountered: