----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74675/#review225866 -----------------------------------------------------------
Ship it! Ship It! - Madhan Neethiraj On Oct. 16, 2023, 6:16 p.m., Christos Bisias wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74675/ > ----------------------------------------------------------- > > (Updated Oct. 16, 2023, 6:16 p.m.) > > > Review request for ranger. > > > Repository: ranger > > > Description > ------- > > Jira: https://issues.apache.org/jira/browse/RANGER-4477 > > Title: RangerOzoneAuthorizer doesn't set the resource owner. > > Description: RangerOzoneAuthorizer doesn't set the Owner user in > RangerAccessResourceImpl and as a result the {OWNER} wildcard always has a > null value. > > We are getting the owner from the context parameter and then setting it as > the resource owner. > > > Diffs > ----- > > > plugin-ozone/src/main/java/org/apache/ranger/authorization/ozone/authorizer/RangerOzoneAuthorizer.java > 12e647ca3 > > > Diff: https://reviews.apache.org/r/74675/diff/1/ > > > Testing > ------- > > This patch was tested using Ranger docker env and Ozone docker env while > debug logs were enabled. Especially this debug log from > `RangerOzoneAuthorizer.checkAccess()` > > ``` > if (LOG.isDebugEnabled()) { > LOG.debug("rangerRequest=" + rangerRequest + ", return=" > + returnValue); > } > ``` > > displays null in the owner before the patch, and the user after the patch is > applied. > > > Thanks, > > Christos Bisias > >
