----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35878/#review89368 -----------------------------------------------------------
Ship it! Ship It! - Tom Beerbower On June 25, 2015, 3:47 p.m., Sumit Mohanty wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/35878/ > ----------------------------------------------------------- > > (Updated June 25, 2015, 3:47 p.m.) > > > Review request for Ambari, Tom Beerbower and Yusaku Sako. > > > Bugs: AMBARI-12131 > https://issues.apache.org/jira/browse/AMBARI-12131 > > > Repository: ambari > > > Description > ------- > > 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. > > > Diffs > ----- > > > ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java > d14cc78 > > ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilterTest.java > a5df47f > > Diff: https://reviews.apache.org/r/35878/diff/ > > > Testing > ------- > > All unit tests for relevant class as well as the full suite. Tested manually > as well. > > > Thanks, > > Sumit Mohanty > >
