Defining a better authentication scheme for Druid and Presto
Right now LDAP is the main gate keeper of data access that is not sufficiently robust as kerberos authentication for Presto and Druid does not carry per-user info.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | mforns | T243309 Add Presto to Analytics' stack | |||
| Open | None | T241189 Defining a better authentication scheme for Druid and Presto | |||
| Declined | None | T242998 VPN access to superset/turnilo instead of LDAP | |||
| Resolved | elukey | T239903 Kerberize Superset to allow Presto queries | |||
| Resolved | cchen | T247329 Learn how to make dashboard on top of data on hadoop/hive via presto |
Event Timeline
Comment Actions
Anyone on LDAP user groups can access now (via presto) anything that is on hive using presto. This conflates somewhat data access opened via LDAP with the privacy of some datasets.
Comment Actions
I think that the title of this task is a little bit misleading. Druid and Presto will need to get Kerberos authentication enabled, the problem will be how to authenticate properly all the UIs that fetch data from them (most notably Superset and Turnilo).