Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authentication support #6

Open
Bernolt opened this issue Jun 13, 2024 · 2 comments
Open

Authentication support #6

Bernolt opened this issue Jun 13, 2024 · 2 comments

Comments

@Bernolt
Copy link

Bernolt commented Jun 13, 2024

Thank you very much for the great work!

Shall we expect to have Databricks client unified authentication supported + profile support ?

@IceRhymers
Copy link

IceRhymers commented Jun 14, 2024

That would be up to databricks. The endpoint used to to get temporary table credentials used here in the code: https://github.com/duckdb/uc_catalog/blob/main/src/uc_api.cpp#L125 is actually not available to use in databricks.
Screenshot 2024-06-14 at 2 40 21 PM

I created a local fork and make some changes to allow for IAM pass-through if you're using normal S3 credentials that duckdb already supports, and it works there. But I wouldn't really count on databricks making it where you can pull your blob storage credentials from their API since it may have more permissions than what Unity Catalog would allow the acting principal.

@lyogev
Copy link

lyogev commented Jun 20, 2024

Super excited about this new UC integration!
However, since temporary-table-credentials is not working, currently I cannot read any table
Getting Error interacting with object store: Generic S3 error: Client error with status 403 Forbidden:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants