Jeroen de Boer

Tried reproducing what @sukhoy94 suggested, only to find that I no longer need to explicitly configure the `controller` in the `route.yaml`. My configuration now looks as follows: security.yaml: ```yaml security:...

I looked into the issue I was experiencing again, and found that by omitting the `controller` in the `route.yaml`, the route 404s if there is no `refresh_token` cookie set. By...

@abeal-hottomali Yup, the code and documentation have already been merged to master, but there hasn't been a release yet since then.

Currently, the latest release is `v1.0.0-beta4`, which was released before this feature was merged. By default, you're reading the documentation on the master branch, where this feature is indeed available....

@abeal-hottomali @byhaskell [v1.0.0 has been released](https://github.com/markitosgv/JWTRefreshTokenBundle/releases/tag/v1.0.0) which includes this work

I think it would be better to have the client periodically explicitly refresh the JWT (by hitting the `/refresh` endpoint with a valid `refresh_token`) rather than have the server do...

I think it would be better to have the client periodically explicitly refresh the JWT (by hitting the `/refresh` endpoint with a valid `refresh_token`) rather than have the server do...

@greenkey-m I think this can be closed as #274 has been merged, making the requested behavior possible see: https://github.com/markitosgv/JWTRefreshTokenBundle#configure-refresh-token-in-cookie

So is there any fix or workaround for this 6-year-old problem? We have a setup where we build packages with normal hyphens (`-`) in the canonical name. For example, we...

> Why don't you run your PHP commands inside the PHP containers instead of on the host? Mostly because it is what I am used to. Running it in the...