You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Rakesh Gupta (Jira)" <ji...@apache.org> on 2024/09/12 10:26:00 UTC
[jira] [Updated] (RANGER-4213) Getting 302 status code instead of 419 in case of session timeout
[ https://issues.apache.org/jira/browse/RANGER-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rakesh Gupta updated RANGER-4213:
---------------------------------
Affects Version/s: 2.6.0
(was: 2.5.0)
> 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)