You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 02:51:00 UTC
Re: [D] How to authenticate Superset with service account [superset]
GitHub user dosubot[bot] edited a comment on the discussion: How to authenticate Superset with service account
<!-- Answer -->
Superset's API does not natively support authenticating with arbitrary external JWT/OIDC tokens (like those issued by Zitadel) for standard API operations such as asset imports. The default and supported approach is still to use session-based authentication: POST to `/api/v1/security/login` with the service account's username and password to obtain a session cookie, then use that cookie to GET `/api/v1/security/csrf_token/` for the CSRF token—just as you did with the default credentials.
If you want to use a Zitadel-issued token directly (for example, as a Bearer token in the Authorization header), Superset would need to be custom-configured with a custom SecurityManager and possibly middleware to validate and accept those tokens. This is an advanced setup and not part of the standard Superset configuration or documentation. There are community discussions and code examples about implementing such custom authentication flows if you want to explore that route further ([example discussion](https://github.com/apache/superset/discussions/33131)).
Unless you have already customized Superset to accept Zitadel tokens, the recommended and supported workflow is to use the service account's username/password with the login endpoint, then proceed as before for asset imports. If you do implement a custom authentication flow, ensure your token is accepted by Superset's authentication system—otherwise, requests to the CSRF endpoint will fail with an authentication error ([reference](https://github.com/apache/superset/issues/32257)).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=5751a6f2-2946-4ff2-82c7-a6ebbcd6e2c8) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34278#discussioncomment-13863472
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org