Michael Babker

Remove the `controller: gesdinet.jwtrefreshtoken::refresh` config from the route. That line is only required for folks using Symfony 4.4 applications and will break a Symfony 6 application because the Security-Guard component...

If you're using the single use option, then the TTL update option really doesn't matter because once a single use token is used, it's destroyed. With TTL update and not...

So disable the ttl_update and single_use options and that’ll get you what you’re looking for.

Yeah, [this line](https://github.com/markitosgv/JWTRefreshTokenBundle/blob/8970ae1a602fb74e434964d03c969d883cfed376/EventListener/AttachRefreshTokenOnSuccessListener.php#L143) looks incorrect. It should probably be `$refreshToken->getValid()->getTimestamp()` to use the expiration time from the token instead of calculating it on each request.

The 1.1 release should fix this.

Which error are you getting? There are a few of them mentioned in this issue. The 1.1 release fixed the routing-related quirks when hitting the refresh endpoint without a refresh...

Usually there’s a stack trace with those deprecations, does that show what’s causing it? It sounds like something is loading the file at some point (maybe something in the framework...

> symfony version - 5.2.5 > Bundle version - v1.0.0-beta4 Please update to Symfony 5.4 and the bundle's 1.1 release and check again.

You'd have to do something to track issued JWTs in your app, out-of-the-box the LexikJWTAuthenticationBundle doesn't have any services to deal with that.

> Are we missing annotations on the Base Class? No. The bundle provides an XML mapping for the base classes for the MongoDB ODM and ORM integrations. Generally, that mapping...