-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
solve the jwt lifecycle problem #6
Comments
Depends on the way we store the token, although it will be stored using local storage or session storage. On click on logout, it will delete the session storage and local session on the client side and there is nothing to do on the client side |
I mean the token that give access to the api It will be always a valid one and if someone keep his token he will always be able to use it |
@rebirthtobi We have to solve the problem of the token life cycle what should be done if the user logout.
should we start those token in the database and delete them in the end of the session.
we need your help tobi
The text was updated successfully, but these errors were encountered: