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

Hudson commented on AMBARI-11590:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2786 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/2786/])
AMBARI-11590. Kerberos: provide option to set test account name (rlevas) 
(rlevas: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ed5558742e4b8b88e495e0190ec1cbe04683ffe1)
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* 
ambari-server/src/main/resources/stacks/HDP/2.2.GlusterFS/services/KERBEROS/configuration/kerberos-env.xml
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* 
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/kerberos-env.xml


> Kerberos: provide option to set test account name
> -------------------------------------------------
>
>                 Key: AMBARI-11590
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11590
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: kerberos
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11590_01.patch, AMBARI-11590_02.patch
>
>
> In many situations with large-scale Active Directory deployments, the 
> krb5.conf is managed outside of Ambari.  This krb5.conf file is configured 
> with all of the DC's in the AD domain, and the outbound requests to the KDC 
> from clients are load balanced across those servers.  In many scenarios the 
> user replication latency causes issues with users not found during the test 
> process.  Due to the fact that we generate a new user every time we test, 
> this can get users to a circular situation in which they can never leave this 
> state because of multi-KDC's in their krb5.conf and delay associated with 
> replication.
> 1) Expose the option to set the test kerberos client principal name (under 
> Advanced kerberos-env)
> 2) Default the value to something unique, but less than 20 characters {code}
> ${cluster_name}-${short_date}
> {code}



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

Reply via email to