-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Superset CSRF Token missing error #22873
Comments
While login with the newest version (Version: 0.0.0-dev), I come up with the same error. There is a useful help on stackoverflow(https://stackoverflow.com/questions/76537655/after-log-in-to-superset-redirect-fialed). But it doesn't work to me. During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Did you manage to solve this? I have the same issue on 3.0. |
Is this issue solved ? I am facing the same error while logging to Superset. |
In config set: |
Same error and login doesn't work. For helm chart adding TALISMAN_ENABLED: "False" to extraEnv In values.yaml fixed the problem.
|
AFTER 3 HOUR!!!! Just this Russian site helped me! TALISMAN_ENABLED = False if you cant find it run this command: |
Thank you!! Saved me precious time. |
@Davidkramer1999 what you're looking at is the API docs, not the Superset UI. Are you accessing this via the documentation website, or via your own Superset instance, e.g. http://localhost:8088/swagger/v1? The latter works for me on current For the original request, you're right that you can turn off Talisman to get around this. Just note that you lose a whole slew of other security safeguards when you do that. It's better to just... provide the token as expected. Closing, as neither of these seem to be a bug (although one of the two is probably a config error), the thread is a bit mixed up now, and both have gone fairly stale. Happy to reopen or tackle in newer, more focused reports with reproducible steps. |
This helped me in superset-config.py |
I get an error when accessing dashboards and only dashboards and not chart like the image beneath,
after tracing error in the superset container i got that error .
I am running superset via k8s helm chart
Refresh CSRF token error │
│ Traceback (most recent call last): │
│ File "/usr/local/lib/python3.8/site-packages/flask_wtf/csrf.py", line 261, in protect │
│ validate_csrf(self._get_csrf_token()) │
│ File "/usr/local/lib/python3.8/site-packages/flask_wtf/csrf.py", line 100, in validate_csrf │
│ raise ValidationError("The CSRF token is missing.") │
│ wtforms.validators.ValidationError: The CSRF token is missing. │
│ │
│ During handling of the above exception, another exception occurred: │
│ │
│ Traceback (most recent call last): │
│ File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1515, in full_dispatch_request │
│ rv = self.preprocess_request() │
│ File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1857, in preprocess_request │
│ rv = self.ensure_sync(before_func)() │
│ File "/usr/local/lib/python3.8/site-packages/flask_wtf/csrf.py", line 229, in csrf_protect │
│ self.protect() │
│ File "/usr/local/lib/python3.8/site-packages/flask_wtf/csrf.py", line 264, in protect │
│ self._error_response(e.args[0]) │
│ File "/usr/local/lib/python3.8/site-packages/flask_wtf/csrf.py", line 307, in _error_response │
│ raise CSRFError(reason) │
│ flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF token is missing.
The text was updated successfully, but these errors were encountered: