[jira] [Updated] (RANGER-4615) Keep the LDAP usersync details popup names same as the backbone js names
[ https://issues.apache.org/jira/browse/RANGER-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4615: Labels: ranger-react (was: ) > Keep the LDAP usersync details popup names same as the backbone js names > > > Key: RANGER-4615 > URL: https://issues.apache.org/jira/browse/RANGER-4615 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Mugdha Varadkar >Priority: Major > Labels: ranger-react > > The data field names are different in the usersync audits sync details popup > in ReactJS when compared to backbone JS. > Ideally, both BackBone JS and React JS field names should be the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4630) Need to add pagination support and searchFilters for tag related APIs
[ https://issues.apache.org/jira/browse/RANGER-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4630: --- Description: Currently for Tag related GET-APIs i.e for (RangerTags,RangerTagDefs,RangerServiceResource) we dont support pagination,and also we need additional searchFilters for them > Need to add pagination support and searchFilters for tag related APIs > - > > Key: RANGER-4630 > URL: https://issues.apache.org/jira/browse/RANGER-4630 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Minor > > Currently for Tag related GET-APIs i.e for > (RangerTags,RangerTagDefs,RangerServiceResource) we dont support > pagination,and also we need additional searchFilters for them -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4630) Need to add pagination support and searchFilters for tag related APIs
[ https://issues.apache.org/jira/browse/RANGER-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4630: -- Assignee: Prashant Satam > Need to add pagination support and searchFilters for tag related APIs > - > > Key: RANGER-4630 > URL: https://issues.apache.org/jira/browse/RANGER-4630 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4630) Need to add pagination support and searchFilters for tag related APIs
Prashant Satam created RANGER-4630: -- Summary: Need to add pagination support and searchFilters for tag related APIs Key: RANGER-4630 URL: https://issues.apache.org/jira/browse/RANGER-4630 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4544) Implement best coding practices for policy resources
[ https://issues.apache.org/jira/browse/RANGER-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4544: Labels: ranger-react (was: ) > Implement best coding practices for policy resources > > > Key: RANGER-4544 > URL: https://issues.apache.org/jira/browse/RANGER-4544 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4593) Upgrade react-bootstrap library
[ https://issues.apache.org/jira/browse/RANGER-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4593: Labels: ranger-react (was: ) > Upgrade react-bootstrap library > --- > > Key: RANGER-4593 > URL: https://issues.apache.org/jira/browse/RANGER-4593 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > Upgrade react-bootstrap library version 1.6.7 to 2.9.1. > This changes also required bootstrap library Upgrade. > so we migrate Bootstrap version 4.6.0 to 5.3.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4582) Improve UI presentation of multiple resources for policy logs in Audit Admin module
[ https://issues.apache.org/jira/browse/RANGER-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4582: Description: Improve UI presentation of multiple resources for policy logs in Audit > Admin Tab *Current Behaviour :-* * Currently for multiple resources we are showing the JSON data as it is in UI under Audit > Admin Tab We can improve by showing the multiple resource JSON data in table format, which can be readable for users. was: Improve UI presentation of multiple resources for policy logs in Audit Admin module * *Current Behaviour :-* Currently for multiple resources we are showing the JSON data as it is in UI at Audit Admin module We can improvise it by showing the multiple resource JSON data in table format, So that it can be readable for user. > Improve UI presentation of multiple resources for policy logs in Audit Admin > module > --- > > Key: RANGER-4582 > URL: https://issues.apache.org/jira/browse/RANGER-4582 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > > Improve UI presentation of multiple resources for policy logs in Audit > > Admin Tab > *Current Behaviour :-* > * Currently for multiple resources we are showing the JSON data as it is in > UI under Audit > Admin Tab > We can improve by showing the multiple resource JSON data in table format, > which can be readable for users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4582) Improve UI presentation of multiple resources for policy logs in Audit > Admin Tab
[ https://issues.apache.org/jira/browse/RANGER-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4582: Summary: Improve UI presentation of multiple resources for policy logs in Audit > Admin Tab (was: Improve UI presentation of multiple resources for policy logs in Audit Admin module) > Improve UI presentation of multiple resources for policy logs in Audit > > Admin Tab > -- > > Key: RANGER-4582 > URL: https://issues.apache.org/jira/browse/RANGER-4582 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > > Improve UI presentation of multiple resources for policy logs in Audit > > Admin Tab > *Current Behaviour :-* > * Currently for multiple resources we are showing the JSON data as it is in > UI under Audit > Admin Tab > We can improve by showing the multiple resource JSON data in table format, > which can be readable for users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4582) Improve UI presentation of multiple resources for policy logs in Audit Admin module
[ https://issues.apache.org/jira/browse/RANGER-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4582: Labels: ranger-react (was: ) > Improve UI presentation of multiple resources for policy logs in Audit Admin > module > --- > > Key: RANGER-4582 > URL: https://issues.apache.org/jira/browse/RANGER-4582 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > > Improve UI presentation of multiple resources for policy logs in Audit Admin > module > * *Current Behaviour :-* > Currently for multiple resources we are showing the JSON data as it is in UI > at Audit Admin module > We can improvise it by showing the multiple resource JSON data in table > format, > So that it can be readable for user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4513) Policy listing page experiences an unexpected reset to Access tab when attempting to filter the service and zone dropdown options
[ https://issues.apache.org/jira/browse/RANGER-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4513: Summary: Policy listing page experiences an unexpected reset to Access tab when attempting to filter the service and zone dropdown options (was: Policy listing page experiences an reset to Access tab when attempting to filter the service and zone dropdown options. ) > Policy listing page experiences an unexpected reset to Access tab when > attempting to filter the service and zone dropdown options > -- > > Key: RANGER-4513 > URL: https://issues.apache.org/jira/browse/RANGER-4513 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4513.patch, 0002-RANGER-4513.patch > > > The policy listing page experiences an unexpected reset when attempting to > filter the service and zone dropdown options. > *Steps to Reproduce:* > # Navigate to the "hive" policy listing page. > # Goto Masking tab > # Select the "Service" dropdown to filter policies based on a specific > service. > # Select the "Zone" dropdown to filter policies based on specific zone. > # Observe that the page resets to the default "Access" tab > *Expected Behavior:* > The page should retain the selected tab when filtering the service and zone > dropdown. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4393) with direct API call, ranger is allowing to add more than 1 dataset in a dataset policy
[ https://issues.apache.org/jira/browse/RANGER-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam resolved RANGER-4393. Resolution: Invalid > with direct API call, ranger is allowing to add more than 1 dataset in a > dataset policy > --- > > Key: RANGER-4393 > URL: https://issues.apache.org/jira/browse/RANGER-4393 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > With direct API call, ranger is allowing to add more than 1 dataset > i.e(datasetName) in a dataset policy. It is blocked from UI. We need to block > it from backend also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[DISCUSS] merge RANGER-3923 branch into master branch
(apologies for the resend; earlier mail had HTML formatting which got lost, now sending in plain text format) Rangers, For more than a year now, Apache Ranger community has been adding significant enhancements in RANGER-3923 branch. These enhancements enable business managers to manage access to datasets, instead of having data owners to manage access to individual resources like tables, columns, files, directories. In addition, this approach offers several benefits including: - reduced time for users in getting access to data across multiple services, with a single policy update. - business managers like project managers to manage access to datasets instead of multiple data owners, which reduces the time taken to get access to data. - separation of responsibilities: data owners focus on building datasets, while business managers focus on managing access to datasets. - eliminate the need to update access policies for any changes in datasets like add/remove/change resources. Apache Ranger community has built APIs and UI to manage datasets and access to datasets. Apache Ranger policy engine has been updated as well to support datasets. I propose merging these enhancements into master branch this week, and work towards releasing Apache Ranger 3.0 version, by next month. Please share your feedback. Looking forward to Apache Ranger 3.0 release! Thanks, Madhan
[DISCUSS] merge RANGER-3923 branch into master branch
Rangers, For more than a year now, Apache Ranger community has been adding significant enhancements in RANGER-3923 branch. These enhancements enable business managers to manage access to datasets, instead of having data owners to manage access to individual resources like tables, columns, files, directories. In addition, this approach offers several benefits including: reduced time for users in getting access to data across multiple services, with a single policy update. business managers like project managers to manage access to datasets instead of multiple data owners, which reduces the time taken to get access to data. separation of responsibilities: data owners focus on building datasets, while business managers focus on managing access to datasets. eliminate the need to update access policies for any changes in datasets like add/remove/change resources. Apache Ranger community has built APIs and UI to manage datasets and access to datasets. Apache Ranger policy engine has been updated as well to support datasets. I propose merging these enhancements into master branch this week, and work towards releasing Apache Ranger 3.0 version, by next month. Please share your feedback. Looking forward to Apache Ranger 3.0 release! Thanks, Madhan
