[
https://issues.apache.org/jira/browse/RANGER-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882656#comment-17882656
]
Mugdha Varadkar commented on RANGER-4213:
-----------------------------------------
master branch commit -
https://github.com/apache/ranger/commit/64738a246e92c17f34c1bfcf6777b7221e2b5bef
ranger-2.6 branch commit -
https://github.com/apache/ranger/commit/91b418df101e61d51e2391a7de63efda618a4eb5
> Getting 302 status code instead of 419 in case of session timeout
> -----------------------------------------------------------------
>
> Key: RANGER-4213
> URL: https://issues.apache.org/jira/browse/RANGER-4213
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 3.0.0, 2.6.0
> Reporter: Mugdha Varadkar
> Assignee: Rakesh Gupta
> Priority: Major
> Attachments: 0001-RANGER-4213.patch
>
>
> Steps to reproduce :
> # Setup a cluster with Ranger Admin code bits
> # Set session timeout to lower value in {{ews/webapp/WEB-INF/web.xml}}
> # Start Ranger Admin
> # When session is timeout the "service/plugins/" api gives status code 302
> instead of 419
> # Earlier we used to get 419 status code from api during session time-out
> cc [~Dhaval.Rajpara] / [~mehul]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
