-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73854/
-----------------------------------------------------------

(Updated Feb. 22, 2022, 4:22 p.m.)


Review request for ranger, Jayendra Parab, Mehul Parikh, Sailaja Polavarapu, 
and Velmurugan Periasamy.


Bugs: RANGER-3629
    https://issues.apache.org/jira/browse/RANGER-3629


Repository: ranger


Description (updated)
-------

Handling permissions during upgrades
Since we are moving to a finer grained privilege model, a 100% mapping will 
likely not be possible.

When a user has solr_admin access type privileges on all collections (*), we 
are mapping it to:
- admin=*->(QERY and UPDATE)
- collection=*->(QERY and UPDATE)
- schemas=*->(QERY and UPDATE)
- configs=*->(QERY and UPDATE)

When a user has solr_admin access type on a particular collection 
collection_name, we are mapping it to
- collection=collection_name->(QERY and UPDATE)
- schemas=collection_name->(QERY and UPDATE)

One should verify their permissions after the upgrade.


Diffs
-----

  security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql b603f96cd 
  security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql 
c111a28f6 
  security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
854a2c676 
  
security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql 
b45eace3b 
  security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql 
adec99857 
  
security-admin/src/main/java/org/apache/ranger/patch/PatchForSolrSvcDefAndPoliciesUpdate_J10055.java
 PRE-CREATION 


Diff: https://reviews.apache.org/r/73854/diff/1/


Testing
-------

Verified upgrade on local/cluser - policies are getting migrated as per 
description.


Thanks,

Mateen Mansoori

Reply via email to