[jira] [Commented] (RANGER-4076) Support Java 17 for build and runtime
[ https://issues.apache.org/jira/browse/RANGER-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17813046#comment-17813046 ] Bhavik Patel commented on RANGER-4076: -- [~rakeshgupta264] have you validated rangeradmin , usersync, tagsync and KMS functionality with JDK-17? > Support Java 17 for build and runtime > - > > Key: RANGER-4076 > URL: https://issues.apache.org/jira/browse/RANGER-4076 > Project: Ranger > Issue Type: New Feature > Components: admin, build-infra >Reporter: Andrew Luo >Priority: Major > Attachments: > 0001-RANGER-4076-Support-Java-17-for-build-and-runtime.patch > > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74858: RANGER-4675: Checkbox selection issue when clicking on permission label in tag-based permissions policy
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74858/ --- (Updated Feb. 1, 2024, 5:13 a.m.) Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4675 https://issues.apache.org/jira/browse/RANGER-4675 Repository: ranger Description --- Checkbox selection issue when clicking on permission label in tag-based permissions policy Current Behaviour :- Their is an inconsistent behaviour in selection of checkbox when click on permission label in tag-based permissions policy. For e.g, select HDFS, HIVE and select permission by clicking on permission label like read, write for both of it, it is observed any change in permission for HIVE it gets impact on HDFS permission selection. Diffs - security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx 38de7fdce Diff: https://reviews.apache.org/r/74858/diff/2/ Testing (updated) --- Applied the patch on a cluster and tested the following UI scenarios :- 1)CRUD operation on policy module Thanks, Brijesh Bhalala
[jira] [Created] (RANGER-4686) Make existing hbase unit test cases to work
Fateh Singh created RANGER-4686: --- Summary: Make existing hbase unit test cases to work Key: RANGER-4686 URL: https://issues.apache.org/jira/browse/RANGER-4686 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Fateh Singh Assignee: Fateh Singh HBase unit tests were ignored in RANGER-2432: Upgrade Hadoop Version to 3.1.1. They need to be reintroduced to prevent regressions while making code changes. They currently fail when trying to create mini hbase cluster -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74860: RANGER-4684 : Need to update createdBy , updatedBy field for gds objects in case the creator is deleted
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74860/#review226193 --- Ship it! Ship It! - Asit Vadhavkar On Jan. 31, 2024, 7:45 a.m., Prashant Satam wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74860/ > --- > > (Updated Jan. 31, 2024, 7:45 a.m.) > > > Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, > Monika Kachhadiya, Siddhesh Phatak, Subhrat Chaudhary, and Vanita Ubale. > > > Bugs: RANGER-4684 > https://issues.apache.org/jira/browse/RANGER-4684 > > > Repository: ranger > > > Description > --- > > Currently when the creator of dataset or any gds Object is deleted from > ranger we get Error as cannot Delete the user because the mapping exist for > the Gds objects for the column addedById, so when the delete operation will > be performed the values for fields createdBy and updatedBy should be changed > from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1 ) > > > Diffs > - > > security-admin/src/main/java/org/apache/ranger/common/db/BaseDao.java > a0ff18948 > > security-admin/src/main/java/org/apache/ranger/service/XPortalUserService.java > 85e457efa > > > Diff: https://reviews.apache.org/r/74860/diff/1/ > > > Testing > --- > > Steps to check > 1) Create user User1 > 2) create a dataset by the User1 account so the createdBy,updatedBy field > will have login Id of user1 > 3) delete this User1 from ranger > 4) Now the values for field createdBy,updatedBy for dataset will change to > "Admin" > > > Thanks, > > Prashant Satam > >
[jira] [Updated] (RANGER-4685) Improvement of drop down messages in policies listing page
[ https://issues.apache.org/jira/browse/RANGER-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pushkar Gogte updated RANGER-4685: -- Environment: apache ranger docker image > Improvement of drop down messages in policies listing page > -- > > Key: RANGER-4685 > URL: https://issues.apache.org/jira/browse/RANGER-4685 > Project: Ranger > Issue Type: Improvement > Components: admin > Environment: apache ranger docker image >Reporter: Pushkar Gogte >Assignee: Anand Nadar >Priority: Minor > Attachments: 2024-01-31_15-44.png, 2024-01-31_15-44_1.png > > > When only one service repo is present in service def in service repo page, > drop down menu should show 'no service repo's to show' instead of 'no options' > Similarly, when no service zone is present, zone name drop down menu should > show 'no security zones' instead of 'no options'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4685) Improvement of drop down messages in policies listing page
[ https://issues.apache.org/jira/browse/RANGER-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pushkar Gogte updated RANGER-4685: -- Component/s: admin (was: Ranger) > Improvement of drop down messages in policies listing page > -- > > Key: RANGER-4685 > URL: https://issues.apache.org/jira/browse/RANGER-4685 > Project: Ranger > Issue Type: Improvement > Components: admin >Reporter: Pushkar Gogte >Assignee: Anand Nadar >Priority: Minor > Attachments: 2024-01-31_15-44.png, 2024-01-31_15-44_1.png > > > When only one service repo is present in service def in service repo page, > drop down menu should show 'no service repo's to show' instead of 'no options' > Similarly, when no service zone is present, zone name drop down menu should > show 'no security zones' instead of 'no options'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4685) Improvement of drop down messages in policies listing page
[ https://issues.apache.org/jira/browse/RANGER-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pushkar Gogte updated RANGER-4685: -- Attachment: 2024-01-31_15-44_1.png 2024-01-31_15-44.png > Improvement of drop down messages in policies listing page > -- > > Key: RANGER-4685 > URL: https://issues.apache.org/jira/browse/RANGER-4685 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pushkar Gogte >Assignee: Anand Nadar >Priority: Minor > Attachments: 2024-01-31_15-44.png, 2024-01-31_15-44_1.png > > > When only one service repo is present in service def in service repo page, > drop down menu should show 'no service repo's to show' instead of 'no options' > Similarly, when no service zone is present, zone name drop down menu should > show 'no security zones' instead of 'no options'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4685) Improvement of drop down messages in policies listing page
[ https://issues.apache.org/jira/browse/RANGER-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pushkar Gogte updated RANGER-4685: -- Attachment: (was: image-2024-01-31-15-43-35-387.png) > Improvement of drop down messages in policies listing page > -- > > Key: RANGER-4685 > URL: https://issues.apache.org/jira/browse/RANGER-4685 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pushkar Gogte >Assignee: Anand Nadar >Priority: Minor > Attachments: 2024-01-31_15-44.png, 2024-01-31_15-44_1.png > > > When only one service repo is present in service def in service repo page, > drop down menu should show 'no service repo's to show' instead of 'no options' > Similarly, when no service zone is present, zone name drop down menu should > show 'no security zones' instead of 'no options'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4685) Improvement of drop down messages in policies listing page
Pushkar Gogte created RANGER-4685: - Summary: Improvement of drop down messages in policies listing page Key: RANGER-4685 URL: https://issues.apache.org/jira/browse/RANGER-4685 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Pushkar Gogte Assignee: Anand Nadar Attachments: image-2024-01-31-15-43-35-387.png When only one service repo is present in service def in service repo page, drop down menu should show 'no service repo's to show' instead of 'no options' Similarly, when no service zone is present, zone name drop down menu should show 'no security zones' instead of 'no options'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4685) Improvement of drop down messages in policies listing page
[ https://issues.apache.org/jira/browse/RANGER-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pushkar Gogte updated RANGER-4685: -- Attachment: image-2024-01-31-15-43-35-387.png > Improvement of drop down messages in policies listing page > -- > > Key: RANGER-4685 > URL: https://issues.apache.org/jira/browse/RANGER-4685 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pushkar Gogte >Assignee: Anand Nadar >Priority: Minor > Attachments: image-2024-01-31-15-43-35-387.png > > > When only one service repo is present in service def in service repo page, > drop down menu should show 'no service repo's to show' instead of 'no options' > Similarly, when no service zone is present, zone name drop down menu should > show 'no security zones' instead of 'no options'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4675) Checkbox selection issue when clicking on permission label in tag-based permissions policy
[ https://issues.apache.org/jira/browse/RANGER-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4675: Attachment: 0002-RANGER-4675.patch > Checkbox selection issue when clicking on permission label in tag-based > permissions policy > > > Key: RANGER-4675 > URL: https://issues.apache.org/jira/browse/RANGER-4675 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4675.patch, 0002-RANGER-4675.patch > > > Checkbox selection issue when clicking on permission label in tag-based > permissions policy > *Current Behaviour :-* > * Their is an inconsistent behaviour in selection of checkbox when click on > permission label in tag-based permissions policy. > * For e.g, select HDFS, HIVE and select permission by clicking on permission > label like read, write for both of it, it is observed any change in > permission for HIVE it gets impact on HDFS permission selection. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4487) HSTS header missing from unsecured API in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4487: -- Attachment: 0002-RANGER-4487.patch > HSTS header missing from unsecured API in Ranger Admin > -- > > Key: RANGER-4487 > URL: https://issues.apache.org/jira/browse/RANGER-4487 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0002-RANGER-4487.patch > > > Currently for unsecured APIs, HSTS header are missing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4487) HSTS header missing from unsecured API in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4487: -- Attachment: (was: 0001-RANGER-4487.patch) > HSTS header missing from unsecured API in Ranger Admin > -- > > Key: RANGER-4487 > URL: https://issues.apache.org/jira/browse/RANGER-4487 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0002-RANGER-4487.patch > > > Currently for unsecured APIs, HSTS header are missing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74710: RANGER-4487: HSTS header missing from unsecured API in Ranger Admin
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74710/ --- (Updated Jan. 31, 2024, 9:36 a.m.) Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Sailaja Polavarapu, and Velmurugan Periasamy. Bugs: RANGER-4487 https://issues.apache.org/jira/browse/RANGER-4487 Repository: ranger Description --- Currently for unsecured APIs, HSTS header are missing. Diffs (updated) - security-admin/src/main/resources/conf.dist/security-applicationContext.xml 738ca16f7 Diff: https://reviews.apache.org/r/74710/diff/2/ Changes: https://reviews.apache.org/r/74710/diff/1-2/ Testing --- HSTS header are present for unsecures APIs Thanks, sanket shelar
[jira] [Updated] (RANGER-4684) Need to update createdBy ,updatedBy field for gds objects in case the creator is deleted
[ https://issues.apache.org/jira/browse/RANGER-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4684: --- Description: Currently when the creator of dataset or any gds Object is deleted from ranger we get Error as cannot Delete the user because the mapping exist for the Gds objects for the column addedById, so when the delete operation will be performed the values for fields createdBy and updatedBy should be changed from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1 ) (was: Currently when the creator of dataset or any gds Object is deleted from ranger we get Error as cannot Delete the user because the mapping exist for the Gds objects for the column addedById, so when the delete operation will be performed the values for fields createdBy and updatedBy should be changed from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1)) > Need to update createdBy ,updatedBy field for gds objects in case the creator > is deleted > > > Key: RANGER-4684 > URL: https://issues.apache.org/jira/browse/RANGER-4684 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently when the creator of dataset or any gds Object is deleted from > ranger we get Error as cannot Delete the user because the mapping exist for > the Gds objects for the column addedById, so when the delete operation will > be performed the values for fields createdBy and updatedBy should be changed > from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1 ) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4684) Need to update createdBy ,updatedBy field for gds objects in case the creator is deleted
[ https://issues.apache.org/jira/browse/RANGER-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4684: -- Assignee: Prashant Satam > Need to update createdBy ,updatedBy field for gds objects in case the creator > is deleted > > > Key: RANGER-4684 > URL: https://issues.apache.org/jira/browse/RANGER-4684 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently when the creator of dataset or any gds Object is deleted from > ranger we get Error as cannot Delete the user because the mapping exist for > the Gds objects for the column addedById, so when the delete operation will > be performed the values for fields createdBy and updatedBy should be changed > from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4425) Need a new API to get history of operations on dataset/datashare requests
[ https://issues.apache.org/jira/browse/RANGER-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek reassigned RANGER-4425: Assignee: Abhishek > Need a new API to get history of operations on dataset/datashare requests > - > > Key: RANGER-4425 > URL: https://issues.apache.org/jira/browse/RANGER-4425 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Subhrat Chaudhary >Assignee: Abhishek >Priority: Major > > Need a new API to get history of Need a new API to get history of operations > on dataset/datashare requests, for the history tab in Dataset/Datashare > details page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4457) Need a new API to get datasets for a resource name like db or column name
[ https://issues.apache.org/jira/browse/RANGER-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek reassigned RANGER-4457: Assignee: Abhishek > Need a new API to get datasets for a resource name like db or column name > - > > Key: RANGER-4457 > URL: https://issues.apache.org/jira/browse/RANGER-4457 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Subhrat Chaudhary >Assignee: Abhishek >Priority: Major > > Need a new API to get get datasets for a resource name like db or column > name. This will be used, when we delete a resource, what all datasets will > affected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
