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

Hadoop QA commented on AMBARI-9014:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12691814/AMBARI-9014_02.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 5 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.

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

This message is automatically generated.

> Design admin principal session expiration handling API call
> -----------------------------------------------------------
>
>                 Key: AMBARI-9014
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9014
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: kdc_credentials, kerberos
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9014_01.patch, AMBARI-9014_02.patch
>
>
> Provide the standard error code that will be returned along with the error 
> message.
> If administrative credentials are not available
> {code:title=400 Bad Request}
> {
>   "status" : 400,
>   "message" : "java.lang.IllegalArgumentException: Missing KDC administrator 
> credentials.\nThe KDC administrator credentials must be set in session by 
> updating the relevant Cluster resource.This may be done by issuing a PUT to 
> the api/v1/clusters/(cluster name) API entry point with the following 
> payload:\n{\n  \"session_attributes\" : {\n    \"kerberos_admin\" : 
> {\"principal\" : \"(PRINCIPAL)\", \"password\" : \"(PASSWORD)\"}\n  }\n}"
> }
> {code}
> If administrative credentials are not valid, for example, incorrect principal 
> or password (or keytab)
> {code:title=400 Bad Request}
> {
>   "status" : 400,
>   "message" : "java.lang.IllegalArgumentException: Invalid KDC administrator 
> credentials.\nThe KDC administrator credentials must be set in session by 
> updating the relevant Cluster resource.This may be done by issuing a PUT to 
> the api/v1/clusters/(cluster name) API entry point with the following 
> payload:\n{\n  \"session_attributes\" : {\n    \"kerberos_admin\" : 
> {\"principal\" : \"(PRINCIPAL)\", \"password\" : \"(PASSWORD)\"}\n  }\n}"
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to