[
https://issues.apache.org/jira/browse/AMBARI-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182087#comment-14182087
]
Hadoop QA commented on AMBARI-7938:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676697/AMBARI-7938.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 4 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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server ambari-views.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/333//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/333//console
This message is automatically generated.
> Views: ability to use current ambari authorization + session
> ------------------------------------------------------------
>
> Key: AMBARI-7938
> URL: https://issues.apache.org/jira/browse/AMBARI-7938
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Fix For: 2.0.0
>
> Attachments: AMBARI-7938.patch
>
>
> When a user accesses ambari, they first "login" with a basic auth
> "Authorization" header. That results in a AMBARISESSIONID= that is
> authenticated. And subsequent calls from Ambari Web use that AMBARISESSIONID
> in a cookie to avoid having to re-auth (as long as the session doesn't
> timeout).
> If a view in ambari web is going to call-out to an ambari server (for
> example, if the view wants to use an ambari server API to update capacity
> scheduler configs via Ambari REST API), it would be useful for that view to
> re-use that auth info / session so the view connects to the ambari server as
> the "same" user.
> Provide a way to expose the "Authorization/session" cookie in viewcontext if
> they plan to have the view connect to an ambari server. Could this be an
> option on URLStreamProvider obtained from the viewcontext, to hide the
> details?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
