You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once done, a user connecting with the proper credentials can only acces the datasources he’s been granted.
Can we achieve the same on lookups ?
We discovered this while connecting Superset to our druid instance : all lookups seem accessible, ,while only the authorized datasources are accessible from Superset logged with the restricted login.
The text was updated successfully, but these errors were encountered:
This sounds like a great feature request! Something similar was done in #11720 to add authorization to system tables. That pattern could be repeated to add support adding authorization on the lookup namespace
Hi, (please consider this as a Feature Request)
We applied Authorization model on datasources, as described here : User authentication and authorization · Apache Druid
Once done, a user connecting with the proper credentials can only acces the datasources he’s been granted.
Can we achieve the same on lookups ?
We discovered this while connecting Superset to our druid instance : all lookups seem accessible, ,while only the authorized datasources are accessible from Superset logged with the restricted login.
The text was updated successfully, but these errors were encountered: