[
https://issues.apache.org/jira/browse/AMBARI-9178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280447#comment-14280447
]
Hadoop QA commented on AMBARI-9178:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12692785/AMBARI-9178.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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1363//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1363//console
This message is automatically generated.
> Implement admin principal session expiration handling
> -----------------------------------------------------
>
> Key: AMBARI-9178
> URL: https://issues.apache.org/jira/browse/AMBARI-9178
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-9178.patch
>
>
> Whenever any API call fails with status 400 and message string that starts
> with java.lang.IllegalArgumentException: Missing KDC administrator
> credentials. or java.lang.IllegalArgumentException: Invalid KDC administrator
> credentials., present the user with a popup (that has save button) asking for
> admin principal and admin password. Once user enters principal and password
> and hits on save button, dismiss the popup and execute the API call to save
> it as session attribute (similar to createKerberosAdminSession function).
> Once this session call succeeds then again trigger the original API call that
> gave the exception.
> The authorization failure that can happen on any API call
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
