[
https://issues.apache.org/jira/browse/RANGER-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332956#comment-15332956
]
rangerqa commented on RANGER-1023:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12810166/0001-RANGER-1023-fixed-redirect-issue-on-keberized-browse.patch
against master revision 2f64837.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
+1 checkstyle. The patch generated 0 code style errors.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-RANGER-Build/245//testReport/
Console output:
https://builds.apache.org/job/PreCommit-RANGER-Build/245//console
This message is automatically generated.
> Handle requests from non-kerberized browser when Ranger is kerberized
> ---------------------------------------------------------------------
>
> Key: RANGER-1023
> URL: https://issues.apache.org/jira/browse/RANGER-1023
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 0.6.0
> Reporter: Velmurugan Periasamy
> Assignee: Selvamohan Neethiraj
> Priority: Critical
> Fix For: 0.6.0
>
> Attachments:
> 0001-RANGER-1023-fixed-redirect-issue-on-keberized-browse.patch
>
>
> *Problem Statement*
> Once Ranger is kerberized, requests to Ranger Admin UI from non-kerberized
> browser hangs on first visit.
> *Workaround*
> Refreshing the ranger admin url twice works, but the original issue needs to
> be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
