[jira] [Updated] (RANGER-4211) CWE-472 present in Host Header
[ https://issues.apache.org/jira/browse/RANGER-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Duran updated RANGER-4211: --- Attachment: Screen Shot 2023-04-12 at 9.59.41 AM.png > CWE-472 present in Host Header > -- > > Key: RANGER-4211 > URL: https://issues.apache.org/jira/browse/RANGER-4211 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Matt Duran >Priority: Major > Attachments: Screen Shot 2023-04-12 at 9.59.41 AM.png > > > When making an HTTP request to the Ranger Admin, it is possible to manipulate > the "Host" header section and have the results appear in the "Location" > header response, creating the possibility of sending a user to a page > controlled by someone else. > CWE-472 recommends verifying inputs that are assumed to be immutable but are > actually externally controllable in order to prevent this or at the very > least combat it. > [https://cwe.mitre.org/data/definitions/472.html] > Is it possible to include a check in the host header to verify that the > location matches the expected host name? Attached is an example of this, as > you can see I've changed the Host section to "google.com" which can be viewed > in the response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4211) CWE-472 present in Host Header
Matt Duran created RANGER-4211: -- Summary: CWE-472 present in Host Header Key: RANGER-4211 URL: https://issues.apache.org/jira/browse/RANGER-4211 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Matt Duran When making an HTTP request to the Ranger Admin, it is possible to manipulate the "Host" header section and have the results appear in the "Location" header response, creating the possibility of sending a user to a page controlled by someone else. CWE-472 recommends verifying inputs that are assumed to be immutable but are actually externally controllable in order to prevent this or at the very least combat it. [https://cwe.mitre.org/data/definitions/472.html] Is it possible to include a check in the host header to verify that the location matches the expected host name? Attached is an example of this, as you can see I've changed the Host section to "google.com" which can be viewed in the response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4199) RangerPluginClassLoader.java has log error
[
https://issues.apache.org/jira/browse/RANGER-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved RANGER-4199.
--
Resolution: Fixed
[~chenyu-opensource] - thank you for the patch. It is now merged in master and
ranger-2.4 branches.
{noformat}
commit 225526931085fd6e67fa48a7a75fd12dc6b709db (HEAD -> master, origin/master,
origin/HEAD)
Author: chenyu-opensource
Date: Fri Apr 21 16:32:33 2023 +0800
RANGER-4199: fixed incorrect log in RangerPluginClassLoader
Signed-off-by: Madhan Neethiraj
{noformat}
{noformat}
commit c21601faeaad0933b58b981f7a320aca0a64a4f4 (HEAD -> ranger-2.4,
origin/ranger-2.4)
Author: chenyu-opensource
Date: Fri Apr 21 16:32:33 2023 +0800
RANGER-4199: fixed incorrect log in RangerPluginClassLoader
Signed-off-by: Madhan Neethiraj
(cherry picked from commit 225526931085fd6e67fa48a7a75fd12dc6b709db)
{noformat}
> RangerPluginClassLoader.java has log error
> --
>
> Key: RANGER-4199
> URL: https://issues.apache.org/jira/browse/RANGER-4199
> Project: Ranger
> Issue Type: Bug
> Components: admin, Ranger
>Reporter: chenyu
>Assignee: chenyu
>Priority: Major
> Fix For: 3.0.0, 2.4.1
>
> Attachments: screenshot-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ranger-plugin-classloader/src/main/java/org/apache/ranger/plugin/classloader/RangerPluginClassLoader.java
> has log error.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Review Request 74408: [RANGER-4199]repair Log Description
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74408/#review225416 --- Ship it! Ship It! - Madhan Neethiraj On April 21, 2023, 9:02 a.m., chen yu wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74408/ > --- > > (Updated April 21, 2023, 9:02 a.m.) > > > Review request for ranger, bhavik patel, Colm O hEigeartaigh, and Madhan > Neethiraj. > > > Bugs: RANGER-4199 > https://issues.apache.org/jira/browse/RANGER-4199 > > > Repository: ranger > > > Description > --- > > repair the wrong Log Description > > > Diffs > - > > > ranger-plugin-classloader/src/main/java/org/apache/ranger/plugin/classloader/RangerPluginClassLoader.java > 2ad56ef2ca > > > Diff: https://reviews.apache.org/r/74408/diff/1/ > > > Testing > --- > > check whether the log display is normal > verified that all existing unit tests pass successfully > > > Thanks, > > chen yu > >
Re: Review Request 74417: RANGER-4197 : Encryption Tab's key manager table show blank data.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74417/#review225415 --- Ship it! Ship It! - Mugdha Varadkar On April 26, 2023, 9:45 a.m., Dhaval Rajpara wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74417/ > --- > > (Updated April 26, 2023, 9:45 a.m.) > > > Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Harshal Chavan, > Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nitin > Galave, Pradeep Agrawal, and Velmurugan Periasamy. > > > Bugs: RANGER-4197 > https://issues.apache.org/jira/browse/RANGER-4197 > > > Repository: ranger > > > Description > --- > > Encryption Tab's key manager table shows blank data in the attributes column. > > > Diffs > - > > > security-admin/src/main/webapp/react-webapp/src/views/Encryption/KeyCreate.jsx > 9b1f05e86 > > security-admin/src/main/webapp/react-webapp/src/views/Encryption/KeyManager.jsx > 2acc3436d > > > Diff: https://reviews.apache.org/r/74417/diff/1/ > > > Testing > --- > > Tested changes on a cluster setup with Ranger Admin build with react code > base. > > > Successful completion of build command : > mvn clean compile package -Psecurity-admin-react > > > Thanks, > > Dhaval Rajpara > >
[jira] [Updated] (RANGER-4210) Use colors for allow/deny users in policy list
[ https://issues.apache.org/jira/browse/RANGER-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Voigt updated RANGER-4210: -- Attachment: ranger.png > Use colors for allow/deny users in policy list > -- > > Key: RANGER-4210 > URL: https://issues.apache.org/jira/browse/RANGER-4210 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kai Voigt >Priority: Minor > Attachments: ranger.png > > > In the list of policies, the Users columns summarises all users affected by > each policy. It would be helpful to color code users with allow permissions > in green, and deny permissions in red. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4210) Use colors for allow/deny users in policy list
Kai Voigt created RANGER-4210: - Summary: Use colors for allow/deny users in policy list Key: RANGER-4210 URL: https://issues.apache.org/jira/browse/RANGER-4210 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kai Voigt In the list of policies, the Users columns summarises all users affected by each policy. It would be helpful to color code users with allow permissions in green, and deny permissions in red. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4210) Use colors for allow/deny users in policy list
[ https://issues.apache.org/jira/browse/RANGER-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Voigt updated RANGER-4210: -- Attachment: (was: Invoice.PDF) > Use colors for allow/deny users in policy list > -- > > Key: RANGER-4210 > URL: https://issues.apache.org/jira/browse/RANGER-4210 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kai Voigt >Priority: Minor > > In the list of policies, the Users columns summarises all users affected by > each policy. It would be helpful to color code users with allow permissions > in green, and deny permissions in red. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4210) Use colors for allow/deny users in policy list
[ https://issues.apache.org/jira/browse/RANGER-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Voigt updated RANGER-4210: -- Attachment: Invoice.PDF > Use colors for allow/deny users in policy list > -- > > Key: RANGER-4210 > URL: https://issues.apache.org/jira/browse/RANGER-4210 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kai Voigt >Priority: Minor > > In the list of policies, the Users columns summarises all users affected by > each policy. It would be helpful to color code users with allow permissions > in green, and deny permissions in red. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4025) Ranger improvement - Roles Import/export API for ranger admin
[ https://issues.apache.org/jira/browse/RANGER-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Gupta updated RANGER-4025: - Attachment: 0006-RANGER-4025.patch > Ranger improvement - Roles Import/export API for ranger admin > - > > Key: RANGER-4025 > URL: https://issues.apache.org/jira/browse/RANGER-4025 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Dineshkumar Yadav >Assignee: Rakesh Gupta >Priority: Major > Attachments: 0006-RANGER-4025.patch > > > Provide API for Roles import/export. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4025) Ranger improvement - Roles Import/export API for ranger admin
[ https://issues.apache.org/jira/browse/RANGER-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Gupta updated RANGER-4025: - Attachment: (was: 0005-RANGER-4025.patch) > Ranger improvement - Roles Import/export API for ranger admin > - > > Key: RANGER-4025 > URL: https://issues.apache.org/jira/browse/RANGER-4025 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Dineshkumar Yadav >Assignee: Rakesh Gupta >Priority: Major > Attachments: 0006-RANGER-4025.patch > > > Provide API for Roles import/export. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74292: RANGER-4025: Ranger improvement - Roles Import/export API for ranger admin
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74292/
---
(Updated April 26, 2023, 10:05 a.m.)
Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay
Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, sanket
shelar, Sailaja Polavarapu, and Velmurugan Periasamy.
Bugs: RANGER-4025
https://issues.apache.org/jira/browse/RANGER-4025
Repository: ranger
Description
---
Provide API for Roles import/export.
Diffs (updated)
-
agents-common/src/main/java/org/apache/ranger/plugin/model/RangerRole.java
682bbd640
security-admin/src/main/java/org/apache/ranger/biz/RoleDBStore.java c19e3e1a1
security-admin/src/main/java/org/apache/ranger/biz/RoleRefUpdater.java
421b2312d
security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java
60903cc97
security-admin/src/main/java/org/apache/ranger/rest/RoleREST.java 4f0edd2b0
security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java
5542250aa
security-admin/src/main/java/org/apache/ranger/view/RangerExportRoleList.java
PRE-CREATION
security-admin/src/main/java/org/apache/ranger/view/RangerPolicyList.java
4799b3f03
security-admin/src/main/java/org/apache/ranger/view/RangerRoleList.java
adbe93db6
security-admin/src/test/java/org/apache/ranger/rest/TestServiceREST.java
9d17553a4
Diff: https://reviews.apache.org/r/74292/diff/6/
Changes: https://reviews.apache.org/r/74292/diff/5-6/
Testing
---
Tested the below Rest API's for Roles import/export to make sure everything
works fine.
RoleREST Rest API :GET /roles/roles/exportJson
RoleREST Rest API :GET
/roles/roles/exportJson?roleName={rolename},{rolename},
RoleREST Rest API :GET /roles/roles/importRolesFromFile
RoleREST Rest API :GET /roles/roles/importRolesFromFile?updateIfExists=true
RoleREST Rest API :GET
/roles/roles/importRolesFromFile?createNonExistUserGroupRole=true
Thanks,
Rakesh Gupta
Review Request 74417: RANGER-4197 : Encryption Tab's key manager table show blank data.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74417/ --- Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Harshal Chavan, Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nitin Galave, Pradeep Agrawal, and Velmurugan Periasamy. Bugs: RANGER-4197 https://issues.apache.org/jira/browse/RANGER-4197 Repository: ranger Description --- Encryption Tab's key manager table shows blank data in the attributes column. Diffs - security-admin/src/main/webapp/react-webapp/src/views/Encryption/KeyCreate.jsx 9b1f05e86 security-admin/src/main/webapp/react-webapp/src/views/Encryption/KeyManager.jsx 2acc3436d Diff: https://reviews.apache.org/r/74417/diff/1/ Testing --- Tested changes on a cluster setup with Ranger Admin build with react code base. Successful completion of build command : mvn clean compile package -Psecurity-admin-react Thanks, Dhaval Rajpara
[jira] [Updated] (RANGER-4197) Encryption Tab's key manager table show blank data.
[ https://issues.apache.org/jira/browse/RANGER-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4197: --- Attachment: 0001-RANGER-4197.patch > Encryption Tab's key manager table show blank data. > --- > > Key: RANGER-4197 > URL: https://issues.apache.org/jira/browse/RANGER-4197 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4197.patch > > > Encryption Tab's key manager table shows blank data in the attributes column. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74371: RANGER-2704 : Support browser login using kerberized authentication Part II
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74371/#review225414 --- Ship it! Ship It! - Dhaval Rajpara On March 30, 2023, 10:29 a.m., Dineshkumar Yadav wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74371/ > --- > > (Updated March 30, 2023, 10:29 a.m.) > > > Review request for ranger, Dhaval Rajpara, Kishor Gollapalliwar, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Pradeep Agrawal, Vishal Suvagia, > and Velmurugan Periasamy. > > > Bugs: RANGER-2704 > https://issues.apache.org/jira/browse/RANGER-2704 > > > Repository: ranger > > > Description > --- > > After session out page is not redirecting to login page > > > Diffs > - > > > security-admin/src/main/java/org/apache/ranger/security/web/filter/RangerSSOAuthenticationFilter.java > 63079d7ca > > > Diff: https://reviews.apache.org/r/74371/diff/1/ > > > Testing > --- > > Testing Done > after applying patch redirecting to login once session out > > > Thanks, > > Dineshkumar Yadav > >
Re: Review Request 74403: RANGER-4194 For Hive service def resources not supporting exclude and recursive are showing this option in service view detail
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74403/#review225413 --- Ship it! Ship It! - Dhaval Rajpara On April 18, 2023, 7:35 p.m., Mugdha Varadkar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74403/ > --- > > (Updated April 18, 2023, 7:35 p.m.) > > > Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, > Mehul Parikh, and Nikunj Pansuriya. > > > Bugs: RANGER-4194 > https://issues.apache.org/jira/browse/RANGER-4194 > > > Repository: ranger > > > Description > --- > > In this review request, updating code logic to not show exclude / recursive > option for resource if not supported in service view page. > > Also fixing below changes : > - Showing warning message when user select UDF resource in Hive. > - Removing dev console.log lines from code. > - Handling console warning shown for unique key props. > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/utils/XAMessages.js > 6570fb7f9b4fa47d3188bc36eba90b29819f629c > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyViewDetails.jsx > cfa838a10ce38d9b7c0485c1b53ad286d45aaed7 > security-admin/src/main/webapp/react-webapp/src/views/CustomBreadcrumb.jsx > 123d7e0861fda062bf87ceecfd32fe2368b97cf6 > security-admin/src/main/webapp/react-webapp/src/views/Header.jsx > 5d3f26ae8035820826e22a6c35ebdc82b20b3905 > security-admin/src/main/webapp/react-webapp/src/views/Layout.jsx > 833f958113406714568990dea6ac7521db7f6271 > > security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/AddUpdatePolicyForm.jsx > b5b2779e0a52fe28c3a2c4cf98220fd0f8cf9fb6 > > security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyConditionsComp.jsx > fc81caecbad44f4f3a46427416fea126b3df9555 > > security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyListing.jsx > 462c5cf210c4a0adead1db760bdc9d9dee6691da > > security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyValidityPeriodComp.jsx > 22ba0fd20549a11058024123c436e1ada1bd54de > > security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx > 8e17fb57ea72474d4a073277fa91a41fe568cecf > > security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx > 5620780bc53f1b582689a41f937589a14d5cefd6 > > security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceDefinitions.jsx > 47ee3f387cbb35bfa843f5c5bdb1bc01d6d79969 > > security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceForm.jsx > 28a98e5c61f567e99d36d3bfa9ea40a37a377993 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/groups_details/GroupForm.jsx > 24fe45675dedd2a4d5c2fec6eee3315a624ae451 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/role_details/RoleForm.jsx > 7d22116c96e79d19d5943eac6906eeb7e35f1674 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/users_details/UserFormComp.jsx > 5b60fa6873d96117a563d3b1bb2714306acf8169 > security-admin/src/main/webapp/react-webapp/src/views/UserProfile.jsx > a1250175408f9477a4ada27512aac2d04eb87d73 > > > Diff: https://reviews.apache.org/r/74403/diff/1/ > > > Testing > --- > > Tested changes on a cluster setup with Ranger Admin build with react code > base. > > Successful completion of build command : > mvn clean compile package -Psecurity-admin-react > > > Thanks, > > Mugdha Varadkar > >
Re: Review Request 74409: RANGER-4183 Updating services fetch call in Zone Display component
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74409/#review225412 --- Ship it! Ship It! - Dhaval Rajpara On April 21, 2023, 9:33 a.m., Mugdha Varadkar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74409/ > --- > > (Updated April 21, 2023, 9:33 a.m.) > > > Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Mehul Parikh, and > Nikunj Pansuriya. > > > Bugs: RANGER-4183 > https://issues.apache.org/jira/browse/RANGER-4183 > > > Repository: ranger > > > Description > --- > > Upon creating a zone, in zone details of respective zone under Service > section table, Service Type column value loads after some millisecond. > > Steps: > Create zone for service say HDFS. > As soon as we click save, zone detail for newly created zone would load, > check the Service Type column. > > > Diffs > - > > > security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/ZoneDisplay.jsx > eac90ca3c6e832c72f9f9c2b521ab56daf0c > > security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/ZoneListing.jsx > 80fa3ea01758979b4e7426870841fb5a400f2bcc > > > Diff: https://reviews.apache.org/r/74409/diff/1/ > > > Testing > --- > > Tested changes on a cluster setup with Ranger Admin build with react code > base. > > Successful completion of build command : > mvn clean compile package -Psecurity-admin-react > > > Thanks, > > Mugdha Varadkar > >
[jira] [Commented] (RANGER-4149) Create common module for HA support
[ https://issues.apache.org/jira/browse/RANGER-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716610#comment-17716610 ] Dineshkumar Yadav commented on RANGER-4149: --- Apache commit : [https://github.com/apache/ranger/commit/5019931d2c4d062c06fe5ddb2ac8d05e2d72da26] > Create common module for HA support > --- > > Key: RANGER-4149 > URL: https://issues.apache.org/jira/browse/RANGER-4149 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Dineshkumar Yadav >Assignee: Dineshkumar Yadav >Priority: Major > > This Common module is implemented using Active/Passive architecture supported > by Apache curator-framework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4086) An admin user without permissions on all permission modules is able to view permissions module page and assign permissions to self
[ https://issues.apache.org/jira/browse/RANGER-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar reassigned RANGER-4086: --- Assignee: Dineshkumar Yadav (was: Dhaval Rajpara) > An admin user without permissions on all permission modules is able to view > permissions module page and assign permissions to self > -- > > Key: RANGER-4086 > URL: https://issues.apache.org/jira/browse/RANGER-4086 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Dineshkumar Yadav >Priority: Major > > On the Ranger UI, create a new admin user and login as the newly created user > in a different browser. > Then remove the permissions for the user on any module. > In the second browser, the newly created user is still able to access the > permissions module page and is able to assign permissions to self. > Ideally, if a user does not have access to all the permission modules, then > the user should not be able to edit permissions, > or if a user tries to remove permissions for an admin user, it should result > in an error or a notification stating that permissions for admin users can't > be removed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4081) [Ranger UI] [React JS] If the url to edit a policy, service or permissions for a module, and the url to view user/group/roles contains an invalid id, then page should
[ https://issues.apache.org/jira/browse/RANGER-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716574#comment-17716574 ] Mugdha Varadkar commented on RANGER-4081: - This need server side change to give response - "No Data Found" and status code - 404 > [Ranger UI] [React JS] If the url to edit a policy, service or permissions > for a module, and the url to view user/group/roles contains an invalid id, > then page should display an error > --- > > Key: RANGER-4081 > URL: https://issues.apache.org/jira/browse/RANGER-4081 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Priority: Major > Labels: ranger-react > > If the url to edit a policy, a service or permissions for a certain module > contains an invalid service id or a policy id, > then the page is stuck in loading state. > Ideally, if the service or a policy for a given id does not exist, then the > page should > display the appropriate error message. > If the url to view the user/group/role details also has an invalid id, the > page is stuck in loading state instead of displaying an error. > For example, if the url to edit a security zone contains an invalid zone id, > there is a popup that displays the message "Data not found for given id". A > similar message should be displayed for other urls with invalid ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4081) [Ranger UI] [React JS] If the url to edit a policy, service or permissions for a module, and the url to view user/group/roles contains an invalid id, then page should d
[ https://issues.apache.org/jira/browse/RANGER-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar reassigned RANGER-4081: --- Assignee: Dineshkumar Yadav > [Ranger UI] [React JS] If the url to edit a policy, service or permissions > for a module, and the url to view user/group/roles contains an invalid id, > then page should display an error > --- > > Key: RANGER-4081 > URL: https://issues.apache.org/jira/browse/RANGER-4081 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Dineshkumar Yadav >Priority: Major > Labels: ranger-react > > If the url to edit a policy, a service or permissions for a certain module > contains an invalid service id or a policy id, > then the page is stuck in loading state. > Ideally, if the service or a policy for a given id does not exist, then the > page should > display the appropriate error message. > If the url to view the user/group/role details also has an invalid id, the > page is stuck in loading state instead of displaying an error. > For example, if the url to edit a security zone contains an invalid zone id, > there is a popup that displays the message "Data not found for given id". A > similar message should be displayed for other urls with invalid ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
