We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Header based auth is insecure.
The text was updated successfully, but these errors were encountered:
It looks like as of now the refresh_token and other details in the auth header payload could be susceptible to XSS and CSRF.
refresh_token
XSS
CSRF
For more reading on the matter - https://security.stackexchange.com/questions/180357/store-auth-token-in-cookie-or-header - it would be a case of also using sameSite to avoid CSRF (was introduced after that article was written).
sameSite
Sorry, something went wrong.
No branches or pull requests
Header based auth is insecure.
The text was updated successfully, but these errors were encountered: