[
https://issues.apache.org/jira/browse/AMBARI-12131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601760#comment-14601760
]
Hudson commented on AMBARI-12131:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3001 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3001/])
AMBARI-12131. API to return information regarding the current user who is
logged in (for SSO) (smohanty) (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=287b7cfde8f261e4c83c527531eb1cbaa774523c)
*
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilterTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java
> 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)
