Michael Babker
Michael Babker
Can't say I'm a fan of the cookie mechanism, but yeah, you'd have to sort the authenticators to make it work since you don't get to control what requests the...
> If I try to use JWT(1) and JWT(2) they both are valid. > > Is this the expected behaviour ? Yes. This bundle on its own doesn't invalidate a...
Ensure you have `symfony/security-guard` installed. Note, the Security Guard component is deprecated in Symfony 5.4 and isn't supported in Symfony 6.
Update your app to use the newer `refresh_jwt` authenticator.
If you're getting an error about the `Symfony\Component\Security\Guard\AbstractGuardAuthenticator` class missing, then something's still trying to use it (maybe not this bundle specifically but somewhere in your app). Try to get...
Remove the `controller:` line from the route definition, it’s not needed with the newer authenticator.
You shouldn't need it, https://github.com/markitosgv/JWTRefreshTokenBundle#define-the-refresh-token-route is pretty much the exact same thing I'm saying here with removing the controller key. https://github.com/markitosgv/JWTRefreshTokenBundle/issues/255#issuecomment-931211151 is the only other time I've seen that one...
> `Unable to find the controller for path "/api/token/refresh".` > `path: /v1/login/refresh` Double-check everything in your configuration and whatever's supposed to be calling the refresh endpoint. Your configuration says the...
That's the exact scenario https://github.com/markitosgv/JWTRefreshTokenBundle/pull/303 fixes.
The 1.1 release should fix this.