[
https://issues.apache.org/jira/browse/RANGER-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042716#comment-15042716
]
Gautam Borad commented on RANGER-765:
-------------------------------------
Committed to master :
https://github.com/apache/incubator-ranger/commit/8057944c2ee659fa3d97969811a59ae9c380eab6
> Handle logout scenario for knox sso disabled case
> -------------------------------------------------
>
> Key: RANGER-765
> URL: https://issues.apache.org/jira/browse/RANGER-765
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.6.0
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 0.6.0
>
> Attachments: RANGER-765.patch
>
>
> *Problem Statement*:
> # *+Case 1+*: For Ranger with knox sso disabled, after logout from
> Ranger, and if the user tries to hit any url related to policy manager, audit
> etc, then it should navigate back to login.jsp page rather then showing 204
> No content Page.
>
> # *+Case 2+*: Currently in RangerSSOAuthenticationFilter.java we are
> assigning all possible authorities to user before authentication. We should
> assign only right authorities to any user according to granted roles to him.
> This should be done only after his successful knoxsso authentication (added
> as part of code cleanup).
> # *+Case 3+*: While manual install of Ranger, sso_enabled property is
> not reflected properly in ranger-admin-site.xml in some scenarios.
> *Steps to reproduce* *+Case 1+* :
> 1. Configure and setup Ranger with knox sso disabled
> 2. login to http://<ipaddress/FQDN>:6080 as some user (e.g : 'admin')
> 3. logout
> 4. paste the following:
> http://<ipaddress/FQDN>:6080/index.html#!/reports/audit/bigData
> *Expected Behaviour*: Should redirect to login page
> *Actual Behaviour*: User will be taken to a 204 No Content page.
> *Steps to reproduce* *+Case 3+* :
> 1. Install Ranger with "sso_enabled" property as "true"
> 2. Check ews/webapp/WEB-INF/classes/conf/ranger-admin-site.xml for
> "ranger.sso.enabled" property value, it is true
> 3. Change the value of "sso_enabled" property as "false" in
> install.properties and run setup.sh
> 4. Check ews/webapp/WEB-INF/classes/conf/ranger-admin-site.xml for
> "ranger.sso.enabled" property value
> *Expected Behaviour*: property value should be "false"
> *Actual Behaviour*: property value is "true"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
