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:54:06 UTC
Re: [D] Pass logged_in_user in superset to Databricks SQL [superset]
GitHub user dosubot[bot] edited a comment on the discussion: Pass logged_in_user in superset to Databricks SQL
<!-- Greeting -->
Hi @bhavishya123! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
Superset does not currently support passing the logged_in_user to Databricks SQL for query execution out-of-the-box. The Databricks engine spec uses a static token-based connection model, always setting the username to "token" and authenticating with the provided access token. There are no built-in hooks or configuration options to dynamically substitute the logged_in_user in the connection URI or connect_args for Databricks connections, and the impersonation features present for other engines like Presto or Trino are not implemented for Databricks [reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/databricks.py).
Superset does have generic impersonation hooks and a new ENGINE_CONTEXT_MANAGER extension point that could, in theory, be customized to implement user-specific connection logic, but this would require custom development and is not available by default [reference](https://github.com/apache/superset/pull/30266).
If you need this feature, it would require extending Superset’s Databricks engine spec or using the ENGINE_CONTEXT_MANAGER to inject user context at connection time, and ensuring Databricks can recognize and enforce RBAC based on that information. There is no built-in or documented workaround for this today.
<!-- 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=888213f7-1b14-4cb1-9074-8e47eed077e8) [](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/34423#discussioncomment-13946797
----
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