[jira] [Updated] (RANGER-4369) [Ranger React UI] Options for permissions pop up for knox policies are not the same in Backbone UI and React JS
[
https://issues.apache.org/jira/browse/RANGER-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brijesh Bhalala updated RANGER-4369:
Attachment: 0001-RANGER-4369.patch
> [Ranger React UI] Options for permissions pop up for knox policies are not
> the same in Backbone UI and React JS
> ---
>
> Key: RANGER-4369
> URL: https://issues.apache.org/jira/browse/RANGER-4369
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Brijesh Bhalala
>Priority: Major
> Labels: ranger-react
> Attachments: 0001-RANGER-4369.patch
>
>
> {color:#172b4d}On backbone JS, when the user tries to create a policy for
> Knox, the permissions pop up box displays only one option, "Allow", but in
> React JS, when the user tries to create a policy for Knox, the permissions
> pop up box contains two options,{color}
> {color:#172b4d}"Allow" and "Select All".{color}
> {color:#172b4d}Ideally, the options in both backbone and react JS should be
> the same,{color}
> {color:#172b4d}and moreover, when only one option is displayed, then "Select
> all" option is not required.{color}
> {color:#172b4d}Hence, it is better to remove the "Select All" option for
> permission pop ups containing only one option.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4369) [Ranger React UI] Options for permissions pop up for knox policies are not the same in Backbone UI and React JS
[
https://issues.apache.org/jira/browse/RANGER-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brijesh Bhalala updated RANGER-4369:
Attachment: (was: 0001-RANGER-4369.patch)
> [Ranger React UI] Options for permissions pop up for knox policies are not
> the same in Backbone UI and React JS
> ---
>
> Key: RANGER-4369
> URL: https://issues.apache.org/jira/browse/RANGER-4369
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Brijesh Bhalala
>Priority: Major
> Labels: ranger-react
> Attachments: 0001-RANGER-4369.patch
>
>
> {color:#172b4d}On backbone JS, when the user tries to create a policy for
> Knox, the permissions pop up box displays only one option, "Allow", but in
> React JS, when the user tries to create a policy for Knox, the permissions
> pop up box contains two options,{color}
> {color:#172b4d}"Allow" and "Select All".{color}
> {color:#172b4d}Ideally, the options in both backbone and react JS should be
> the same,{color}
> {color:#172b4d}and moreover, when only one option is displayed, then "Select
> all" option is not required.{color}
> {color:#172b4d}Hence, it is better to remove the "Select All" option for
> permission pop ups containing only one option.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4369) [Ranger React UI] Options for permissions pop up for knox policies are not the same in Backbone UI and React JS
[
https://issues.apache.org/jira/browse/RANGER-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brijesh Bhalala updated RANGER-4369:
Attachment: 0001-RANGER-4369.patch
> [Ranger React UI] Options for permissions pop up for knox policies are not
> the same in Backbone UI and React JS
> ---
>
> Key: RANGER-4369
> URL: https://issues.apache.org/jira/browse/RANGER-4369
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Brijesh Bhalala
>Priority: Major
> Labels: ranger-react
> Attachments: 0001-RANGER-4369.patch
>
>
> {color:#172b4d}On backbone JS, when the user tries to create a policy for
> Knox, the permissions pop up box displays only one option, "Allow", but in
> React JS, when the user tries to create a policy for Knox, the permissions
> pop up box contains two options,{color}
> {color:#172b4d}"Allow" and "Select All".{color}
> {color:#172b4d}Ideally, the options in both backbone and react JS should be
> the same,{color}
> {color:#172b4d}and moreover, when only one option is displayed, then "Select
> all" option is not required.{color}
> {color:#172b4d}Hence, it is better to remove the "Select All" option for
> permission pop ups containing only one option.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Review Request 74590: RANGER-4369: Options for permissions pop up for knox policies are not the same in Backbone UI and React JS
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74590/ --- Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4369 https://issues.apache.org/jira/browse/RANGER-4369 Repository: ranger Description --- On backbone JS, when the user tries to create a policy for Knox, the permissions pop up box displays only one option, "Allow", but in React JS, when the user tries to create a policy for Knox, the permissions pop up box contains two options, "Allow" and "Select All". Ideally, the options in both backbone and react JS should be the same, and moreover, when only one option is displayed, then "Select all" option is not required. Hence, it is better to remove the "Select All" option for permission pop ups containing only one option. Diffs - security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx 4e98134ab security-admin/src/main/webapp/react-webapp/src/styles/style.css aaa54a380 security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyPermissionItem.jsx 821d39370 Diff: https://reviews.apache.org/r/74590/diff/1/ Testing --- Tested changes on a cluster setup with Ranger Admin build with React JS code base. Verfified the permission items in service and policy module. Successful completion of build command : mvn clean compile package -Psecurity-admin-react Thanks, Brijesh Bhalala
Ranger XXAccessAuditv4 issue with Java 11
Hi Team I am using ranger 2.1.0 and trying to. upgrade to JAVA 11 for the same but I am seeing following issue in Ranger logs while ranger startup happens . It seems some XXAccessAuditV4 primary key annotation issue, when I checked its parent i.e XXAccessAuditBase I see @ID annotation for the parent already present, does anyone has any clues on this issue ? or has someone observed it before? [ERROR ] [main] org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:426) Failed to initialize JPA EntityManagerFactory: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.EntityManagerSetupException|Exception Description: Predeployment of PersistenceUnit [defaultPU] failed.|Internal Exception: Exception [EclipseLink-7161] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.ValidationException|Exception Description: Entity class [class org.apache.ranger.entity.XXAccessAuditV4] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy. Thanks in advance. Regards, Nikhil Purbhe
[jira] [Resolved] (RANGER-4334) [Ranger UI] [React JS] Options for permissions pop up for knox policies are not the same in Backbone UI and React JS
[ https://issues.apache.org/jira/browse/RANGER-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala resolved RANGER-4334. - Resolution: Duplicate > [Ranger UI] [React JS] Options for permissions pop up for knox policies are > not the same in Backbone UI and React JS > > > Key: RANGER-4334 > URL: https://issues.apache.org/jira/browse/RANGER-4334 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > > On backbone JS, when the user tries to create a policy for Knox, the > permissions pop up box displays only one option, "Allow", but in React JS, > when the user tries to create a policy for Knox, the permissions pop up box > contains two options, > "Allow" and "Select All". > Ideally, the options in both backbone and react JS should be the same, > and moreover, when only one option is displayed, then "Select all" option is > not required. > Hence, it is better to remove the "Select All" option for permission pop ups > containing only one option. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74593: RANGER-4358: Keep the usersync details popup names same as the backbone js names
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74593/ --- Review request for ranger, Dhaval Rajpara and Mugdha Varadkar. Bugs: RANGER-4358 https://issues.apache.org/jira/browse/RANGER-4358 Repository: ranger Description --- The data field names are different in the usersync audits sync details popup in ReactJS when compared to backbone JS. Ideally, both of them should be the same and the field names in React JS should be the same as in BackBone JS. Diffs - security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/SyncSourceDetails.jsx 42a886ef3 Diff: https://reviews.apache.org/r/74593/diff/1/ Testing --- Built Ranger admin with the changes and verified the behaviour in React UI Thanks, Abhishek Patil
[jira] [Updated] (RANGER-4304) Update swagger version in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4304: Attachment: 0001-RANGER-4304-ranger-site.patch > Update swagger version in Ranger > > > Key: RANGER-4304 > URL: https://issues.apache.org/jira/browse/RANGER-4304 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Arnout Engelen >Assignee: Mugdha Varadkar >Priority: Major > Attachments: 0001-RANGER-4304-ranger-site.patch, > 0001-RANGER-4304.patch, 0002-RANGER-4304.patch > > > The Ranger website embeds a Swagger UI, AFAICS currently version 2.2.10. > Older versions of swagger, such as this one, suffer from a number of security > weaknesses. > > While fortunately [https://ranger.apache.org|https://ranger.apache.org/] does > not have any sensitive cookies or login mechanism or similar, so there isn't > really anything to compromise, it would be good to update to a recent version > of Swagger. Could you look into that? > > It is somewhat unclear to me whether the ranger site is maintained in SVN > ([https://svn.apache.org/viewvc/ranger/site/)] or git > ([https://github.com/apache/ranger-site]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4304) Update swagger version in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763639#comment-17763639 ] Mugdha Varadkar commented on RANGER-4304: - This jira is in handling two fixes, # Updating the swagger version in Ranger Admin server - https://reviews.apache.org/r/74577/ # Updating the swagger version in [Ranger Site|https://ranger.apache.org/apidocs/ui/index.html] - [^0001-RANGER-4304-ranger-site.patch] [~sneethiraj] Request you to review and help in merging [^0001-RANGER-4304-ranger-site.patch] in https://github.com/apache/ranger-site for updating swagger version to 5.4.2 (https://ranger.apache.org/apidocs/ui/index.html) > Update swagger version in Ranger > > > Key: RANGER-4304 > URL: https://issues.apache.org/jira/browse/RANGER-4304 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Arnout Engelen >Assignee: Mugdha Varadkar >Priority: Major > Attachments: 0001-RANGER-4304-ranger-site.patch, > 0001-RANGER-4304.patch, 0002-RANGER-4304.patch > > > The Ranger website embeds a Swagger UI, AFAICS currently version 2.2.10. > Older versions of swagger, such as this one, suffer from a number of security > weaknesses. > > While fortunately [https://ranger.apache.org|https://ranger.apache.org/] does > not have any sensitive cookies or login mechanism or similar, so there isn't > really anything to compromise, it would be good to update to a recent version > of Swagger. Could you look into that? > > It is somewhat unclear to me whether the ranger site is maintained in SVN > ([https://svn.apache.org/viewvc/ranger/site/)] or git > ([https://github.com/apache/ranger-site]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74577: RANGER-4304: Update swagger version in Ranger
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74577/#review225727 --- Ship it! Ship It! - Dhaval Shah On Sept. 5, 2023, 12:34 p.m., Mugdha Varadkar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74577/ > --- > > (Updated Sept. 5, 2023, 12:34 p.m.) > > > Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, > Mehul Parikh, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4304 > https://issues.apache.org/jira/browse/RANGER-4304 > > > Repository: ranger > > > Description > --- > > Upgrading the swagger version to the latest available - 5.4.2 > > > Diffs > - > > docs/src/site/resources/swagger-ui-bundle.js > 89bf4a9b3b0fda8de929f1052ddca98abc644ffa > docs/src/site/resources/swagger-ui-es-bundle-core.js > cf16c6a8891d1ff509c5f53beace292e5c7e88c9 > docs/src/site/resources/swagger-ui-es-bundle.js > 328d693f6b21481511305dc6e11bbc0202417e55 > docs/src/site/resources/swagger-ui-standalone-preset.js > 39df72f598045eeae2eeb79ca5f9110857c5a16f > docs/src/site/resources/swagger-ui.css > 267c5e141d0ae033dcfb6ce95c348d61b9b0fa47 > docs/src/site/resources/swagger-ui.js > 3a4f99719ed281d854af25b98b87c1b797b58c49 > docs/src/site/resources/swagger.html > 726b8d8f58bf013d65aef1c779c0f5e16a8a3322 > > > Diff: https://reviews.apache.org/r/74577/diff/2/ > > > Testing > --- > > Tested changes on a cluster setup with Ranger Admin build with React JS code > base. > > Successful completion of build command : > mvn clean compile package -Psecurity-admin-react > > > Thanks, > > Mugdha Varadkar > >
Re: Review Request 74577: RANGER-4304: Update swagger version in Ranger
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74577/#review225728 --- Ship it! Ship It! - Brijesh Bhalala On Sept. 5, 2023, 12:34 p.m., Mugdha Varadkar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74577/ > --- > > (Updated Sept. 5, 2023, 12:34 p.m.) > > > Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, > Mehul Parikh, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4304 > https://issues.apache.org/jira/browse/RANGER-4304 > > > Repository: ranger > > > Description > --- > > Upgrading the swagger version to the latest available - 5.4.2 > > > Diffs > - > > docs/src/site/resources/swagger-ui-bundle.js > 89bf4a9b3b0fda8de929f1052ddca98abc644ffa > docs/src/site/resources/swagger-ui-es-bundle-core.js > cf16c6a8891d1ff509c5f53beace292e5c7e88c9 > docs/src/site/resources/swagger-ui-es-bundle.js > 328d693f6b21481511305dc6e11bbc0202417e55 > docs/src/site/resources/swagger-ui-standalone-preset.js > 39df72f598045eeae2eeb79ca5f9110857c5a16f > docs/src/site/resources/swagger-ui.css > 267c5e141d0ae033dcfb6ce95c348d61b9b0fa47 > docs/src/site/resources/swagger-ui.js > 3a4f99719ed281d854af25b98b87c1b797b58c49 > docs/src/site/resources/swagger.html > 726b8d8f58bf013d65aef1c779c0f5e16a8a3322 > > > Diff: https://reviews.apache.org/r/74577/diff/2/ > > > Testing > --- > > Tested changes on a cluster setup with Ranger Admin build with React JS code > base. > > Successful completion of build command : > mvn clean compile package -Psecurity-admin-react > > > Thanks, > > Mugdha Varadkar > >
Re: Review Request 74577: RANGER-4304: Update swagger version in Ranger
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74577/#review225729 --- Ship it! Ship It! - Dhaval Rajpara On Sept. 5, 2023, 12:34 p.m., Mugdha Varadkar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74577/ > --- > > (Updated Sept. 5, 2023, 12:34 p.m.) > > > Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, > Mehul Parikh, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4304 > https://issues.apache.org/jira/browse/RANGER-4304 > > > Repository: ranger > > > Description > --- > > Upgrading the swagger version to the latest available - 5.4.2 > > > Diffs > - > > docs/src/site/resources/swagger-ui-bundle.js > 89bf4a9b3b0fda8de929f1052ddca98abc644ffa > docs/src/site/resources/swagger-ui-es-bundle-core.js > cf16c6a8891d1ff509c5f53beace292e5c7e88c9 > docs/src/site/resources/swagger-ui-es-bundle.js > 328d693f6b21481511305dc6e11bbc0202417e55 > docs/src/site/resources/swagger-ui-standalone-preset.js > 39df72f598045eeae2eeb79ca5f9110857c5a16f > docs/src/site/resources/swagger-ui.css > 267c5e141d0ae033dcfb6ce95c348d61b9b0fa47 > docs/src/site/resources/swagger-ui.js > 3a4f99719ed281d854af25b98b87c1b797b58c49 > docs/src/site/resources/swagger.html > 726b8d8f58bf013d65aef1c779c0f5e16a8a3322 > > > Diff: https://reviews.apache.org/r/74577/diff/2/ > > > Testing > --- > > Tested changes on a cluster setup with Ranger Admin build with React JS code > base. > > Successful completion of build command : > mvn clean compile package -Psecurity-admin-react > > > Thanks, > > Mugdha Varadkar > >
[jira] [Commented] (RANGER-4304) Update swagger version in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763643#comment-17763643 ] Dhaval Shah commented on RANGER-4304: - Hi , Merged in Apache Master : https://github.com/apache/ranger/commit/0f7af3a6cc8aa49770e3ffa3d290ac7d7f7510df Thanks > Update swagger version in Ranger > > > Key: RANGER-4304 > URL: https://issues.apache.org/jira/browse/RANGER-4304 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Arnout Engelen >Assignee: Mugdha Varadkar >Priority: Major > Attachments: 0001-RANGER-4304-ranger-site.patch, > 0001-RANGER-4304.patch, 0002-RANGER-4304.patch > > > The Ranger website embeds a Swagger UI, AFAICS currently version 2.2.10. > Older versions of swagger, such as this one, suffer from a number of security > weaknesses. > > While fortunately [https://ranger.apache.org|https://ranger.apache.org/] does > not have any sensitive cookies or login mechanism or similar, so there isn't > really anything to compromise, it would be good to update to a recent version > of Swagger. Could you look into that? > > It is somewhat unclear to me whether the ranger site is maintained in SVN > ([https://svn.apache.org/viewvc/ranger/site/)] or git > ([https://github.com/apache/ranger-site]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74594: RANGER:3923 : API to get DataShare id, name List
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74594/ --- Review request for ranger, Anand Nadar, Madhan Neethiraj, and Subhrat Chaudhary. Bugs: RANGER-3923 https://issues.apache.org/jira/browse/RANGER-3923 Repository: ranger Description --- API to fetch Map of id,names for datashare Diffs - agents-common/src/main/java/org/apache/ranger/plugin/store/GdsStore.java 53fe55336 security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java d2bd0789d security-admin/src/main/java/org/apache/ranger/rest/GdsREST.java 653e397d4 security-admin/src/main/java/org/apache/ranger/security/context/RangerAPIList.java de9014072 Diff: https://reviews.apache.org/r/74594/diff/1/ Testing --- Add multiple datashares then will able to fetch map of id,names for datashare Thanks, Prashant Satam
Re: Review Request 74593: RANGER-4358: Keep the usersync details popup names same as the backbone js names
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74593/ --- (Updated Sept. 11, 2023, 11:14 a.m.) Review request for ranger, Dhaval Rajpara and Mugdha Varadkar. Bugs: RANGER-4358 https://issues.apache.org/jira/browse/RANGER-4358 Repository: ranger Description --- The data field names are different in the usersync audits sync details popup in ReactJS when compared to backbone JS. Ideally, both of them should be the same and the field names in React JS should be the same as in BackBone JS. Diffs (updated) - security-admin/src/main/webapp/react-webapp/src/utils/XAEnums.js 6e5eb0d5b security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/SyncSourceDetails.jsx 42a886ef3 Diff: https://reviews.apache.org/r/74593/diff/2/ Changes: https://reviews.apache.org/r/74593/diff/1-2/ Testing --- Built Ranger admin with the changes and verified the behaviour in React UI Thanks, Abhishek Patil
Re: Review Request 74593: RANGER-4358: Keep the usersync details popup names same as the backbone js names
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74593/#review225730 --- Ship it! Ship It! - Mugdha Varadkar On Sept. 11, 2023, 11:14 a.m., Abhishek Patil wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74593/ > --- > > (Updated Sept. 11, 2023, 11:14 a.m.) > > > Review request for ranger, Dhaval Rajpara and Mugdha Varadkar. > > > Bugs: RANGER-4358 > https://issues.apache.org/jira/browse/RANGER-4358 > > > Repository: ranger > > > Description > --- > > The data field names are different in the usersync audits sync details popup > in ReactJS when compared to backbone JS. > Ideally, both of them should be the same and the field names in React JS > should be the same as in BackBone JS. > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/utils/XAEnums.js 6e5eb0d5b > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/SyncSourceDetails.jsx > 42a886ef3 > > > Diff: https://reviews.apache.org/r/74593/diff/2/ > > > Testing > --- > > Built Ranger admin with the changes and verified the behaviour in React UI > > > Thanks, > > Abhishek Patil > >
Re: Review Request 74593: RANGER-4358: Keep the usersync details popup names same as the backbone js names
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74593/#review225731 --- Ship it! Ship It! - Dhaval Rajpara On Sept. 11, 2023, 11:14 a.m., Abhishek Patil wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74593/ > --- > > (Updated Sept. 11, 2023, 11:14 a.m.) > > > Review request for ranger, Dhaval Rajpara and Mugdha Varadkar. > > > Bugs: RANGER-4358 > https://issues.apache.org/jira/browse/RANGER-4358 > > > Repository: ranger > > > Description > --- > > The data field names are different in the usersync audits sync details popup > in ReactJS when compared to backbone JS. > Ideally, both of them should be the same and the field names in React JS > should be the same as in BackBone JS. > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/utils/XAEnums.js 6e5eb0d5b > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/SyncSourceDetails.jsx > 42a886ef3 > > > Diff: https://reviews.apache.org/r/74593/diff/2/ > > > Testing > --- > > Built Ranger admin with the changes and verified the behaviour in React UI > > > Thanks, > > Abhishek Patil > >
[jira] [Updated] (RANGER-4358) Data field names are different in usersync audits popup in ReactJS
[
https://issues.apache.org/jira/browse/RANGER-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek updated RANGER-4358:
-
Fix Version/s: 3.0.0
> Data field names are different in usersync audits popup in ReactJS
> --
>
> Key: RANGER-4358
> URL: https://issues.apache.org/jira/browse/RANGER-4358
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
> Labels: ranger-react
> Fix For: 3.0.0
>
>
> {color:#172b4d}The data field names are different in the usersync audits sync
> details popup in ReactJS when compared to backbone JS.{color}
> {color:#172b4d}Ideally, both of them should be the same and the field names
> in React JS should be the same as in BackBone JS.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4358) Keep the usersync details popup names same as the backbone js names
[
https://issues.apache.org/jira/browse/RANGER-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated RANGER-4358:
Summary: Keep the usersync details popup names same as the backbone js
names (was: Data field names are different in usersync audits popup in ReactJS)
> Keep the usersync details popup names same as the backbone js names
> ---
>
> Key: RANGER-4358
> URL: https://issues.apache.org/jira/browse/RANGER-4358
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
> Labels: ranger-react
> Fix For: 3.0.0
>
>
> {color:#172b4d}The data field names are different in the usersync audits sync
> details popup in ReactJS when compared to backbone JS.{color}
> {color:#172b4d}Ideally, both of them should be the same and the field names
> in React JS should be the same as in BackBone JS.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4304) Update swagger version in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4304: Attachment: (was: 0001-RANGER-4304-ranger-site.patch) > Update swagger version in Ranger > > > Key: RANGER-4304 > URL: https://issues.apache.org/jira/browse/RANGER-4304 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Arnout Engelen >Assignee: Mugdha Varadkar >Priority: Major > Attachments: 0001-RANGER-4304.patch, 0002-RANGER-4304.patch > > > The Ranger website embeds a Swagger UI, AFAICS currently version 2.2.10. > Older versions of swagger, such as this one, suffer from a number of security > weaknesses. > > While fortunately [https://ranger.apache.org|https://ranger.apache.org/] does > not have any sensitive cookies or login mechanism or similar, so there isn't > really anything to compromise, it would be good to update to a recent version > of Swagger. Could you look into that? > > It is somewhat unclear to me whether the ranger site is maintained in SVN > ([https://svn.apache.org/viewvc/ranger/site/)] or git > ([https://github.com/apache/ranger-site]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4304) Update swagger version in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4304: Attachment: 0001-RANGER-4304-ranger-site.patch > Update swagger version in Ranger > > > Key: RANGER-4304 > URL: https://issues.apache.org/jira/browse/RANGER-4304 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Arnout Engelen >Assignee: Mugdha Varadkar >Priority: Major > Attachments: 0001-RANGER-4304-ranger-site.patch, > 0001-RANGER-4304.patch, 0002-RANGER-4304.patch > > > The Ranger website embeds a Swagger UI, AFAICS currently version 2.2.10. > Older versions of swagger, such as this one, suffer from a number of security > weaknesses. > > While fortunately [https://ranger.apache.org|https://ranger.apache.org/] does > not have any sensitive cookies or login mechanism or similar, so there isn't > really anything to compromise, it would be good to update to a recent version > of Swagger. Could you look into that? > > It is somewhat unclear to me whether the ranger site is maintained in SVN > ([https://svn.apache.org/viewvc/ranger/site/)] or git > ([https://github.com/apache/ranger-site]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4403) update security-zone validation to prevent duplicate resource entries
Madhan Neethiraj created RANGER-4403: Summary: update security-zone validation to prevent duplicate resource entries Key: RANGER-4403 URL: https://issues.apache.org/jira/browse/RANGER-4403 Project: Ranger Issue Type: Improvement Components: admin Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj Currently it is possible to add a resource multiple times in a security zone - for example add path=/test multiple times in a security-zone. Though this doesn't impact the enforcement of policies defined in the security-zone, it will be easier to manage zones if duplicate resource entries are allowed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74597: RANGER-4403: security-zone validation updated to prevent duplicate resource entries
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74597/ --- Review request for ranger, Anand Nadar, Abhay Kulkarni, Mehul Parikh, Monika Kachhadiya, Pradeep Agrawal, Ramesh Mani, and Subhrat Chaudhary. Bugs: RANGER-4403 https://issues.apache.org/jira/browse/RANGER-4403 Repository: ranger Description --- updated security zone validation to prevent duplicate resource entries Diffs - agents-common/src/main/java/org/apache/ranger/plugin/errors/ValidationErrorCode.java d8c214c0f agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPolicyResourceSignature.java c14811867 agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerSecurityZoneValidator.java 970055511 agents-common/src/test/java/org/apache/ranger/plugin/model/validation/RangerSecurityZoneValidatorTest.java 1a1c30517 Diff: https://reviews.apache.org/r/74597/diff/1/ Testing --- - added unit tests - verified that all existing tests pass successfully Thanks, Madhan Neethiraj
[jira] [Updated] (RANGER-4403) update security-zone validation to prevent duplicate resource entries
[ https://issues.apache.org/jira/browse/RANGER-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated RANGER-4403: - Attachment: RANGER-4403.patch > update security-zone validation to prevent duplicate resource entries > - > > Key: RANGER-4403 > URL: https://issues.apache.org/jira/browse/RANGER-4403 > Project: Ranger > Issue Type: Improvement > Components: admin >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-4403.patch > > > Currently it is possible to add a resource multiple times in a security zone > - for example add path=/test multiple times in a security-zone. Though this > doesn't impact the enforcement of policies defined in the security-zone, it > will be easier to manage zones if duplicate resource entries are allowed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4404) Audit to hdfs for orc format feature stabilisation
Bhavik Patel created RANGER-4404:
Summary: Audit to hdfs for orc format feature stabilisation
Key: RANGER-4404
URL: https://issues.apache.org/jira/browse/RANGER-4404
Project: Ranger
Issue Type: Improvement
Components: audit
Affects Versions: 2.4.0, 3.0.0
Reporter: Bhavik Patel
Assignee: Bhavik Patel
Currently if we have 50GB audit log file in spool directory then it is taking
4-5hr for the conversion and writing to HDFS.
Also, we are observing below error logs
{code:java}
ERROR [AuditFileQueueSpool_hdfs_destWriter] provider.BaseAuditHandler: Error
writing to log file.
java.lang.RuntimeException: Overflow of newLength.
smallBuffer.length=1073741824, nextElemLength=38
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.increaseBufferSpace(BytesColumnVector.java:311)
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.setVal(BytesColumnVector.java:182)
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.setVal(BytesColumnVector.java:207)
at org.apache.ranger.audit.utils.ORCFileUtil.log(ORCFileUtil.java:143)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter$1.run(RangerORCAuditWriter.java:77)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter$1.run(RangerORCAuditWriter.java:73)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1762)
at
org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:541)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.logAuditAsORC(RangerORCAuditWriter.java:73)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.logAsORC(RangerORCAuditWriter.java:159)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.log(RangerORCAuditWriter.java:112)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:78)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.log(HDFSAuditDestination.java:163)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.sendEvent(AuditFileQueueSpool.java:926)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.logEvent(AuditFileQueueSpool.java:913)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.runLogAudit(AuditFileQueueSpool.java:847)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.run(AuditFileQueueSpool.java:790)
{code}
hive-storage-api version upgrade(>=2.7.3) required to resolve the above error.
Current version is 2.7.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4404) Audit to hdfs for orc format feature stabilisation
[
https://issues.apache.org/jira/browse/RANGER-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhavik Patel updated RANGER-4404:
-
Description:
Currently if we have 50GB audit log file in spool directory then it is taking
4-5hr for the conversion and writing to HDFS.
Also, we are observing below error logs
{code:java}
ERROR [AuditFileQueueSpool_hdfs_destWriter] provider.BaseAuditHandler: Error
writing to log file.
java.lang.RuntimeException: Overflow of newLength.
smallBuffer.length=1073741824, nextElemLength=38
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.increaseBufferSpace(BytesColumnVector.java:311)
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.setVal(BytesColumnVector.java:182)
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.setVal(BytesColumnVector.java:207)
at org.apache.ranger.audit.utils.ORCFileUtil.log(ORCFileUtil.java:143)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter$1.run(RangerORCAuditWriter.java:77)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter$1.run(RangerORCAuditWriter.java:73)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1762)
at
org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:541)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.logAuditAsORC(RangerORCAuditWriter.java:73)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.logAsORC(RangerORCAuditWriter.java:159)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.log(RangerORCAuditWriter.java:112)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:78)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.log(HDFSAuditDestination.java:163)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.sendEvent(AuditFileQueueSpool.java:926)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.logEvent(AuditFileQueueSpool.java:913)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.runLogAudit(AuditFileQueueSpool.java:847)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.run(AuditFileQueueSpool.java:790)
{code}
hive-storage-api version upgrade(>=2.7.3) required to resolve the above error.
Current version is 2.7.2
cc: [~rmani] [~fateh288]
was:
Currently if we have 50GB audit log file in spool directory then it is taking
4-5hr for the conversion and writing to HDFS.
Also, we are observing below error logs
{code:java}
ERROR [AuditFileQueueSpool_hdfs_destWriter] provider.BaseAuditHandler: Error
writing to log file.
java.lang.RuntimeException: Overflow of newLength.
smallBuffer.length=1073741824, nextElemLength=38
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.increaseBufferSpace(BytesColumnVector.java:311)
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.setVal(BytesColumnVector.java:182)
at
org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.setVal(BytesColumnVector.java:207)
at org.apache.ranger.audit.utils.ORCFileUtil.log(ORCFileUtil.java:143)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter$1.run(RangerORCAuditWriter.java:77)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter$1.run(RangerORCAuditWriter.java:73)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1762)
at
org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:541)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.logAuditAsORC(RangerORCAuditWriter.java:73)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.logAsORC(RangerORCAuditWriter.java:159)
at
org.apache.ranger.audit.utils.RangerORCAuditWriter.log(RangerORCAuditWriter.java:112)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:78)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.log(HDFSAuditDestination.java:163)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.sendEvent(AuditFileQueueSpool.java:926)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.logEvent(AuditFileQueueSpool.java:913)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.runLogAudit(AuditFileQueueSpool.java:847)
at
org.apache.ranger.audit.queue.AuditFileQueueSpool.run(AuditFileQueueSpool.java:790)
{code}
hive-storage-api version upgrade(>=2.7.3) required to resolve the above error.
Current version is 2.7.2
> Audit to hdfs for orc format feature stabilisation
> -
[jira] [Assigned] (RANGER-4397) API to get DataShare id,name List
[ https://issues.apache.org/jira/browse/RANGER-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4397: -- Assignee: Prashant Satam > API to get DataShare id,name List > - > > Key: RANGER-4397 > URL: https://issues.apache.org/jira/browse/RANGER-4397 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
