You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling the /me endpoint looks up the current user in the database again. We now use the username to do this instead of the ID. We set the username in the 'id' attribute during denormalization, and then a custom data provider. This was because during fixture reloads the ID changes.
As we are re-checking the database though, it seems a good time to unset the JWT token if the user no longer exists, otherwise future requests would still be authenticated as using the tokens is stateless auth.
The text was updated successfully, but these errors were encountered:
Calling the /me endpoint looks up the current user in the database again. We now use the username to do this instead of the ID. We set the username in the 'id' attribute during denormalization, and then a custom data provider. This was because during fixture reloads the ID changes.
As we are re-checking the database though, it seems a good time to unset the JWT token if the user no longer exists, otherwise future requests would still be authenticated as using the tokens is stateless auth.
The text was updated successfully, but these errors were encountered: