ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhaval Rajpara (JIRA)" <j...@apache.org>
Subject [jira] [Created] (RANGER-2285) Error page is not available when API call returns HTTP status code 403(forbidden)
Date Thu, 15 Nov 2018 06:18:00 GMT
Dhaval Rajpara created RANGER-2285:
--------------------------------------

             Summary: 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
             Fix For: master


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)

Mime
View raw message