GitHub user dosubot[bot] added a comment to 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).*

---
<sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/888213f7-1b14-4cb1-9074-8e47eed077e8?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/888213f7-1b14-4cb1-9074-8e47eed077e8?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/888213f7-1b14-4cb1-9074-8e47eed077e8?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/888213f7-1b14-4cb1-9074-8e47eed077e8?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/888213f7-1b14-4cb1-9074-8e47eed077e8?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/888213f7-1b14-4cb1-9074-8e47eed077e8?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/888213f7-1b14-4cb1-9074-8e47eed077e8?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
 nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34423)

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-unsubscr...@superset.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to