zachjsh 3bb67721f7 Allow for Input source security in SQL layer (#13989) ... This change introduces the concept of input source type security model, proposed in #13837.. With this change, this feature is only available at the SQL layer, but we will expand to native layer in a follow up PR. To enable this feature, the user must set the following property to true: druid.auth.enableInputSourceSecurity=true The default value for this property is false, which will continue the existing functionality of having the usage all external sources being authorized against the hardcoded resource action new ResourceAction(new Resource(ResourceType.EXTERNAL, ResourceType.EXTERNAL), Action.READ When this config is enabled, the users will be required to be authorized for the following resource action new ResourceAction(new Resource(ResourceType.EXTERNAL, {INPUT_SOURCE_TYPE}, Action.READ where {INPUT_SOURCE_TYPE} is the type of the input source being used;, http, inline, s3, etc.. Documentation has not been added for the feature as it is not complete at the moment, as we still need to enable this for the native layer in a follow up pr.		2023-03-29 22:15:33 -04:00
..
src	Allow for Input source security in SQL layer (#13989)	2023-03-29 22:15:33 -04:00
pom.xml	merge druid-core, extendedset, and druid-hll into druid-processing to simplify everything (#13698)	2023-02-17 14:27:41 -08:00