ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11858) Ambari web UI keeps challenging users to re-log in
Date Thu, 11 Jun 2015 13:13:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-11858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581910#comment-14581910
] 

Hadoop QA commented on AMBARI-11858:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12739042/AMBARI-11858.patch
  against trunk revision .

    {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 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/Ambari-trunk-test-patch/3139//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3139//console

This message is automatically generated.

> Ambari web UI keeps challenging users to re-log in
> --------------------------------------------------
>
>                 Key: AMBARI-11858
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11858
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11858.patch
>
>
> If the authenticated flag is stored in the persist API as false (dont know how it happens)
then refreshing browser navigates the authenticated user to the login page instead of navigating
to the refreshed page in the App.
> As part of this ticket:
> # Makes sure that authenticated flag in localdb is saved per user 
> # authenticated flag should not be stored in the API persist call and so should not get
overridden by the persist data on logging in.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message