[GitHub] [druid] zachjsh commented on issue #13837: Input source security model for MSQ table functions and more

["zachjsh (via GitHub)" <gi...@apache.org>]

zachjsh commented on issue #13837:
URL: https://github.com/apache/druid/issues/13837#issuecomment-1442555517

   thanks for the writeup @paul-rogers . This seems like a great idea! 
   
   One question / concern I had is how this would handle the case where users were previously relying on reasource action `(EXTERNAL, EXTERNAL, READ)` to read from any inputSource type? During upgrade, we could maybe migrate such a permission for users / roles to give permissions to all configured input source types configured at that time, just as an example. Wondering if you considered this and what idea you may have around this?


-- 
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: commits-unsubscribe@druid.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org