[
https://issues.apache.org/jira/browse/RANGER-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved RANGER-5564.
--------------------------------------
Fix Version/s: 3.0.0
2.9.0
Resolution: Fixed
master branch:
https://github.com/apache/ranger/commit/ef3442560eab3114f6852d1760a4bbe9a19a0cb4
ranger-2.9 branch:
https://github.com/apache/ranger/commit/902964c6f7db895e59ab8606e852423467d9ee72
> update RangerAuthzConfig to support properties from plugin configuration files
> ------------------------------------------------------------------------------
>
> Key: RANGER-5564
> URL: https://issues.apache.org/jira/browse/RANGER-5564
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 3.0.0, 2.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{RangerAuthzConfig}} is used in {{RangerEmbeddedAuthorizer}} to provide
> following configuration sets from properties loaded from
> {{ranger-embedded-authz.properties}} file, which start with
> {{{}ranger.authz.{}}}:
> # plugin specific configurations that typically start with
> {{ranger.plugin.<service-type>>}}
> # audit configurations that typically start with {{xasecure.audit.}}
>
> Updating {{RangerAuthzConfig}} to process properties loaded from following
> plugin configuration files will make it easier to replace
> {{RangerBasePlugin}} usage with {{{}RangerEmbeddedAuthorizer{}}}, while
> retaining existing configuration files:
> # ranger-<service-type>-security.xml
> # ranger-<service-type>-audit.xml
> # ranger-policymgr-ssl.xml
>
> In addition to processing properties that start with {{{}ranger.authz.{}}},
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
