Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 11 Jun 2015 12:55:00 +0000 (UTC)
From: "Aleksandr Kovalenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12837128.1434027260000.45577.1434027300522@Atlassian.JIRA>
In-Reply-To: <JIRA.12837128.1434027260000@Atlassian.JIRA>
References: <JIRA.12837128.1434027260000@Atlassian.JIRA>
 <JIRA.12837128.1434027260651@arcas>
Subject: [jira] [Created] (AMBARI-11858) Ambari web UI keeps challenging
 users to re-log in
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksandr Kovalenko created AMBARI-11858:
--------------------------------------------

             Summary: 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


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)