[
https://issues.apache.org/jira/browse/RANGER-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805389#comment-17805389
]
Rakesh Gupta edited comment on RANGER-4213 at 1/11/24 12:44 PM:
----------------------------------------------------------------
[~vishalsuvagia] please review this RR as it handles Ranger UI session-timeout
functionality, which is broken by
https://issues.apache.org/jira/browse/RANGER-2704
was (Author: JIRAUSER298658):
[~vishalsuvagia] please review this RR as it's breaking Ranger UI
session-timeout functionality.
> 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
> 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)
