jon-wei commented on issue #9380: URL: https://github.com/apache/druid/issues/9380#issuecomment-624993739
For resource types and names, I'm thinking about them as such: - Resource types would be a category of entities/information being accessed, like DATASOURCE or SERVER - If the resource type has sub-items like DATASOURCE, then additionally it'd have resource names. Using the examples in the spreadsheet, I would probably go with something like: - Removing STATE/CONFIG as resource types, I think they're redundant - Keep DATASOURCE as a resource type - What were formerly resource names under the STATE/CONFIG types would now just be top-level resource types - Maybe we could have a single blanket resource type for INTERNAL without finer-grained resource names, I don't think there'd be much reason to set fine-grained permissions on that level given that the internal APIs aren't meant to be called by users > I need to think more about this, it would be helpful if we start by taking one persona like Data engineer - write down types and names for the APIs that he will be using and define permissions for him in format Aciton:Type:Name(if we are keeping the format same). That sounds good, it would probably help guide our thoughts on what the core resource types should be. > Somehow allow input source specific user credentials to be passed to downstream system from which data is read to enable do as functionality. This seems complex and intrusive. Yeah, that does seem like it could be tricky to handle. > Use Druid permission model by introducing INPUTSOURCE Resource Type and corresponding Resource Name will be provided by implementations of InputSource interface. On task submission input source permission will be checked. I have a prototype code here - https://github.com/apache/druid/compare/master...pjain1:ingestion_security?expand=1#diff-40bbee918ab4b9fe487c02c4dfd1989d That approach seems reasonable to me at a high level, I'll take a look at the prototype. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
