Michael Babker
Michael Babker
The 1.1 release fixed this.
With 1.1 this isn't all that bad to pull off: 1) Make sure you've got an entity set up in your app adding the device name field 2) Replace or...
Please try with the 1.1 release. The issue shouldn't have been the Accept header, but other quirks fixed with the release.
The 1.1 tag includes this option.
The doc blocks should be fixed up after https://github.com/markitosgv/JWTRefreshTokenBundle/pull/259 I didn’t think about it before, but breaking the inheritance on the Doctrine manager would be OK here (technically it’s a...
Try omitting the controller from the route definition, so use this: ``` api_token_refresh: path: /api/token/refresh ``` (I don't remember if it's 100% necessary to have a route configured in the...
> Thanks for the suggestion @mbabker, but without the controller in the route definition I get the following error: I just noticed your `access_control` section doesn’t have an entry for...
https://github.com/mbabker/refresh-token-tester is the local app I've been using to validate a lot of the changes I make here in a full Symfony app. I don't have the issue with Symfony...
IIRC, if your application has multiple user providers, you always have to explicitly set the “provider” key when either on the firewall or the authenticator; that’s a Symfony convention and...
If I had to guess, the 404 is because the authenticator only reports as supporting the request if it can extract a token from the request and since the authenticator...