-
Notifications
You must be signed in to change notification settings - Fork 927
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
After token expiration the authorization header on axios still presents #172
After token expiration the authorization header on axios still presents #172
Comments
I think it should be handled on LOCAL Scheme implementation. The LOCAL Scheme should implement a built-in refresh token policy. Of course, the backend also should handle the "refresh token" policy. For OAUTH2 Scheme a solution was proposed. Waiting approval. |
I wonder what happened to this issue? |
@metawise there are too many open PR from community, but I think the Maintainers are busy with other packages. This module is pretty important, a must have for any application. Would be nice if they come back :) |
@robsontenorio We did not forget any of you. |
Fix released with v4.9.0. |
Version
v4.3.0
Reproduction link
https://github.com/nuxt-community/auth-module
Steps to reproduce
I use local strategy with a token. After the token expires if i reload the page, the user is logged out because i have resetOnError=True, but in all request made with axios the authorization header with the expired token is still present and all request return 401.
What is expected ?
After token expiration the auth header in axios must be removed.
What is actually happening?
The auth header is still present and all request fail.
The text was updated successfully, but these errors were encountered: