dosubot[bot] commented on issue #31283: URL: https://github.com/apache/superset/issues/31283#issuecomment-2516601561
<!-- Answer --> I found a similar discussion regarding CSRF token issues in Superset, which might be relevant to your situation. The discussion titled "[QA][superset & keycloak] flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF token is missing](https://github.com/apache/superset/discussions/28250)" addresses a similar error. A suggested solution from a related closed issue was to set `TALISMAN_ENABLED` to `False` in the configuration, which resolved the problem for multiple users <sup>[[1]](https://github.com/apache/superset/discussions/28250)</sup>. Additionally, ensure that the CSRF token is correctly fetched and included in the headers for API requests. In Superset's Celery task for cache warming, the `fetch_csrf_token` function is used to update the headers with the CSRF token before making the API request <sup>[[2]](https://github.com/apache/superset/blob/master/superset/tasks/cache.py)</sup>. You might want to verify that this process is correctly implemented in your setup. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
