Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 24 Jun 2015 17:48:05 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12840271.1435168019000.4968.1435168085038@Atlassian.JIRA>
In-Reply-To: <JIRA.12840271.1435168019000@Atlassian.JIRA>
References: <JIRA.12840271.1435168019000@Atlassian.JIRA>
 <JIRA.12840271.1435168019767@arcas>
Subject: [jira] [Updated] (AMBARI-12131) API to return information regarding
 the current user who is logged in (for SSO)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-12131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sumit Mohanty updated AMBARI-12131:
-----------------------------------
    Attachment: AMBARI-12131.patch

> API to return information regarding the current user who is logged in (for SSO)
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-12131
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12131
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12131.patch
>
>
> This is a scenario where a gateway sits in front of the ambari server host and provides initial authentication and then forwards the message to the ambari-server. As the gateway has logged the user, the FE needs to know the name of the logged on user.
> From the UI side we cannot read request headers using javascript, we can only read response headers and write to request headers. In this case we cannot get info about what user is currently logged in. 
> BE can send the current user name in response header.


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