[jira] [Commented] (AMBARI-22293) Improve KDC integration

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-22293:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12895075/AMBARI-22293_trunk_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 12 new or modified test files.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

      {color:red}-1 javac{color}.  The applied patch generated 512 javac compiler warnings (more than the trunk's current 506 warnings).

    {color:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server ambari-web:

                  org.apache.ambari.server.serveraction.kerberos.IPAKerberosOperationHandlerTest
                  org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandlerTest

                                      The test build failed in [ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12590//artifact/patch-work/testrun_ambari-web.txt] 

Javac warnings: https://builds.apache.org/job/Ambari-trunk-test-patch/12590//artifact/patch-work/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12590//console

This message is automatically generated.

> Improve KDC integration
> -----------------------
>
>                 Key: AMBARI-22293
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22293
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Major
>              Labels: kerberos
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-22293_trunk_01.patch, AMBARI-22293_trunk_02.patch
>
>
> Improve KDC integration by making the interfaces more consistent with each other.
> *Notes:*
> * When using the MIT KDC or IPA options, the {{kerberos-env/admin_server_host}} value *must be the fully qualified domain name* (FQDN) of the host were the KDC administrator service is. 
> * When connecting to the MIT KDC and IPA server, a username a password is not used to authenticate using the kadmin utility.  A Kerberos ticket is first acquired and that is used for authentication.
> * When creating Kerberos identities using the MIT KDC and IPA handlers, the Ambari-generated password is not used.  All password's for principals in the MIT KDC and IP server are generated randomly by the KDC.
> * Removed {{kerberos-env/set_password_expiry}} and {{kerberos-env/password_chat_timeout}} properties since they are no longer needed
> * Changed {{kerberos-env/groups}} to {{kerberos-env/ipa_user_groups}} to be more explicit in how the property is used.
> * The setPassword implementation for the MIT KDC and IPA handlers do nothing except check to see if the relevant principal exists. This is to maintain backward compatibility with previous implementations.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)