[jira] [Updated] (RANGER-2285) Error page is not available when API call returns HTTP status code 403(forbidden)
[ https://issues.apache.org/jira/browse/RANGER-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-2285: Fix Version/s: (was: master) > Error page is not available when API call returns HTTP status code > 403(forbidden) > -- > > Key: RANGER-2285 > URL: https://issues.apache.org/jira/browse/RANGER-2285 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Minor > Attachments: > 0001-RANGER-2285-Error-page-is-not-available-when-API-cal.patch, > 0002-RANGER-2285.patch, 403ErrorPage.png, screenshort_1.png, screenshort_2.png > > > Error page not populated when getting response 403(Forbidden). > scenario-1 > Steps - > 1. Login with admin. > 2. Create users 'testuser3' and 'testuser2' with USER_ROLE. > 3. Create a group 'group1'. > 4. Add 'testuser3' and testuser2' to 'group1'. > 5. Give 'User/Group' page permission to 'testuser1' > 6. Login with 'testuser3' > 7. Go to group listing page > 8. Click on 'view user' button in group listing page. > 9. Click on 'testuser2' username (The page goes into loading state instant > off error page ). > (Refer image screenshort_1) > scenario-2 > Steps - > 1. Login with 'testuser3'. > 2. 'testuser3' user does not have permission to view Tag base policy. > 3. By changing the router to '/policymanager/tag' its show blank 'Service > Manager' page instant off error page. > (Refer image screenshort_2). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2285) Error page is not available when API call returns HTTP status code 403(forbidden)
[ https://issues.apache.org/jira/browse/RANGER-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-2285: --- Attachment: 0002-RANGER-2285.patch > Error page is not available when API call returns HTTP status code > 403(forbidden) > -- > > Key: RANGER-2285 > URL: https://issues.apache.org/jira/browse/RANGER-2285 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Minor > Fix For: master > > Attachments: > 0001-RANGER-2285-Error-page-is-not-available-when-API-cal.patch, > 0002-RANGER-2285.patch, 403ErrorPage.png, screenshort_1.png, screenshort_2.png > > > Error page not populated when getting response 403(Forbidden). > scenario-1 > Steps - > 1. Login with admin. > 2. Create users 'testuser3' and 'testuser2' with USER_ROLE. > 3. Create a group 'group1'. > 4. Add 'testuser3' and testuser2' to 'group1'. > 5. Give 'User/Group' page permission to 'testuser1' > 6. Login with 'testuser3' > 7. Go to group listing page > 8. Click on 'view user' button in group listing page. > 9. Click on 'testuser2' username (The page goes into loading state instant > off error page ). > (Refer image screenshort_1) > scenario-2 > Steps - > 1. Login with 'testuser3'. > 2. 'testuser3' user does not have permission to view Tag base policy. > 3. By changing the router to '/policymanager/tag' its show blank 'Service > Manager' page instant off error page. > (Refer image screenshort_2). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (RANGER-2285) Error page is not available when API call returns HTTP status code 403(forbidden)
[ https://issues.apache.org/jira/browse/RANGER-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-2285: --- Attachment: 0001-RANGER-2285-Error-page-is-not-available-when-API-cal.patch 403ErrorPage.png > Error page is not available when API call returns HTTP status code > 403(forbidden) > -- > > Key: RANGER-2285 > URL: https://issues.apache.org/jira/browse/RANGER-2285 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Minor > Fix For: master > > Attachments: > 0001-RANGER-2285-Error-page-is-not-available-when-API-cal.patch, > 403ErrorPage.png, screenshort_1.png, screenshort_2.png > > > Error page not populated when getting response 403(Forbidden). > scenario-1 > Steps - > 1. Login with admin. > 2. Create users 'testuser3' and 'testuser2' with USER_ROLE. > 3. Create a group 'group1'. > 4. Add 'testuser3' and testuser2' to 'group1'. > 5. Give 'User/Group' page permission to 'testuser1' > 6. Login with 'testuser3' > 7. Go to group listing page > 8. Click on 'view user' button in group listing page. > 9. Click on 'testuser2' username (The page goes into loading state instant > off error page ). > (Refer image screenshort_1) > scenario-2 > Steps - > 1. Login with 'testuser3'. > 2. 'testuser3' user does not have permission to view Tag base policy. > 3. By changing the router to '/policymanager/tag' its show blank 'Service > Manager' page instant off error page. > (Refer image screenshort_2). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2285) Error page is not available when API call returns HTTP status code 403(forbidden)
[ https://issues.apache.org/jira/browse/RANGER-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-2285: --- Attachment: screenshort_1.png screenshort_2.png > Error page is not available when API call returns HTTP status code > 403(forbidden) > -- > > Key: RANGER-2285 > URL: https://issues.apache.org/jira/browse/RANGER-2285 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Minor > Fix For: master > > Attachments: screenshort_1.png, screenshort_2.png > > > Error page not populated when getting response 403(Forbidden). > scenario-1 > Steps - > 1. Login with admin. > 2. Create users 'testuser3' and 'testuser2' with USER_ROLE. > 3. Create a group 'group1'. > 4. Add 'testuser3' and testuser2' to 'group1'. > 5. Give 'User/Group' page permission to 'testuser1' > 6. Login with 'testuser3' > 7. Go to group listing page > 8. Click on 'view user' button in group listing page. > 9. Click on 'testuser2' username (The page goes into loading state instant > off error page ). > (Refer image screenshort_1) > scenario-2 > Steps - > 1. Login with 'testuser3'. > 2. 'testuser3' user does not have permission to view Tag base policy. > 3. By changing the router to '/policymanager/tag' its show blank 'Service > Manager' page instant off error page. > (Refer image screenshort_2). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
