[GitHub] [superset] dpgaspar commented on pull request #17337: feat: Adds a key-value store endpoint for Superset

[GitBox <gi...@apache.org>]

dpgaspar commented on pull request #17337:
URL: https://github.com/apache/superset/pull/17337#issuecomment-965200100


   > Thanks @michael-s-molina - if we do implement the "anyone with a key" model, we should throw some restrictions or confirmation around it so it's very clear to the user that they're about to share very widely. Something to think about on the UI-side of the house.
   
   Would definitely fall to restrict access to the owner of the key. but the K/V store goal is not clear yet or it's just too broad. Session management and caching are sensitive, caching values could potentially defeat dataset ownership and RBAC permissions.
   
   We can make the ownership restriction optional and on by default behind a config key. Or discuss this further on a secure sharing model  
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org