ambari-dev mailing list archives

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

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

Hudson commented on AMBARI-11858:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #6 (See [https://builds.apache.org/job/Ambari-branch-2.1/6/])
AMBARI-11858. Ambari web UI keeps challenging users to re-log in (akovalenko) (akovalenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3b71475b86422f7de878f58533c1dec4f8f85989)
* ambari-web/app/models/cluster_states.js


> 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