Destination Improvement: Support finer grained access controls for Databricks Destination
The Databricks destination when using SQL endpoints requires users to provide an access token from the databricks workspace that has broad table ACLs enabled on it. (Full r/w access on the data catalog). Would be ideal if the table ACLs required could be limited to a specific set of databases/tables.
-
Official comment
Hi Anup,
Thanks for your post in this portal, this is Kevin from the product team! I agree with you that we should follow a principle of least privileges when it comes to access to these systems. I will be sure to follow up with our engineering team to understand if we can minimize the requirements for the Fivetran user.
Could you share which permissions are most concerning from the list that werequire? Are there specific steps or access rights that are a concern?
Thanks!
Please sign in to leave a comment.
Comments
1 comment