ACL for lookups
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 58m
- Merged PRs (30d)
- 233
Description
Hi, (please consider this as a Feature Request)
We applied Authorization model on datasources, as described here : [User authentication and authorization · Apache Druid](https://druid.apache.org/docs/latest/operations/security-user-auth.html)
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.
Contributor guide
Research direction
Start with the linked Druid user authentication and authorization documentation, then reproduce the restricted-login case against lookups described in the issue. Compare lookup access with datasource ACL behavior, including the Superset connection; done means the intended authorization boundary for restricted users is clearly defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100