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:26 UTC
Re: [D] Unable to connect to Dremio instance [superset]
GitHub user dosubot[bot] edited a comment on the discussion: Unable to connect to Dremio instance
<!-- Greeting -->
Hi @danieljimenez! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
Superset's Dremio integration supports both username/password and token-based authentication for Arrow Flight, but the default code and some examples use a token in the connection string rather than username/password. The error you're seeing—`Flight returned unauthenticated error`—is surfaced directly from the driver and usually means the authentication method or credentials in the connection string don't match what Dremio expects for Arrow Flight connections. Superset doesn't add any custom logic here; it just passes your connection string to the driver and surfaces any errors it returns [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/dremio.py).
The official docs and code show two patterns: one with username/password in the URI (like you're using), and another with a `Token=<TOKEN>` parameter. The code's default placeholder uses token-based authentication [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/dremio.py). Datagrip may be handling Arrow Flight authentication differently under the hood, which could explain why it works there but not in Superset.
Here are some concrete troubleshooting steps:
- Try switching to token-based authentication in your connection string:
`dremio+flight://dremio-client.data.svc.cluster.local:32010/dremio?Token=<YOUR_TOKEN>&UseEncryption=false`
(replace `<YOUR_TOKEN>` with your Dremio personal access token).
- If you must use username/password, double-check for any special characters in your credentials and ensure they're properly URL-encoded [[source]](https://github.com/apache/superset/issues/25501).
- If your Dremio instance is configured to require tokens for Arrow Flight, username/password won't work.
- You can also try adding advanced connection parameters in the "Extra" field in Superset's database config, if your environment requires it [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/configuration/databases.mdx).
If the issue persists, check the Dremio server logs for more details on why authentication is failing. Let me know if switching to token-based authentication resolves the error.
<!-- 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=1216c1a5-ed9e-4d2a-ba4e-15057c77da34) [](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/34527#discussioncomment-13977211
----
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