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

Hadoop QA commented on AMBARI-12131:
------------------------------------

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

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  
org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcherTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3261//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3261//console

This message is automatically generated.

> 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)

Reply via email to