Markus Podar

Just to clarify, tokens by itself are stateless and can't be invalidated. But yes, "invalidation" is possible by adding them to the "blacklist", thus my questions: - do you have...

> Besides, i try to downgrade PHP to version 7 and change the jwt package back to tymon package, the token invalidate is working fine after logged out. Thanks, that's...

@eschricker sorry, missed this myself Why does enable the exception for logging purpose "fix" the issue? Wouldn't that be a bug in itself? 🤔

> It also caches authenticated user in `JWTGuard`, which causes user to be not updated between requests I already sense semantically breaking change and we should probably target 2.x for...

I've a "but" here: the original library didn't claim Octane compatibility and doing so suddenly for essentially (still) the same code base would bring 1.x into the realm of requiring...

TBH I don't see the connection between "PHP version support", "laravel version support" and "octane support". I was just suggesting that, in case we need to change too much for...

> (I believe here in GitHub there's something called project it's similar to Asana) A project is "more" than just what we need here, not sure if there's a benefit....

> I don't know how the milestones in GitHub work I essence, you - create a new milestone: https://github.com/PHP-Open-Source-Saver/jwt-auth/milestones/new - then apply it to respective issues/PRs  This is a...

The changes on the PR look legit to me (briefly looked; I've also made a lib Octane-compatible some time ago and they make sense).

Thanks, yes, makes sense to include this topic into the discussion over at https://github.com/PHP-Open-Source-Saver/jwt-auth/discussions/76#discussioncomment-2012665