-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34919/
-----------------------------------------------------------
Review request for Ambari, Emil Anca, Robert Nettleton, and Tom Beerbower.
Bugs: AMBARI-11590
https://issues.apache.org/jira/browse/AMBARI-11590
Repository: ambari
Description
-------
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
`${cluster_name}-${short_date}`
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
ad76ffa
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
dc5fc75
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/kerberos-env.xml
ec50f69
ambari-server/src/main/resources/stacks/HDP/2.2.GlusterFS/services/KERBEROS/configuration/kerberos-env.xml
31833cb
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
684cdd4
Diff: https://reviews.apache.org/r/34919/diff/
Testing
-------
Manually tested.
#Jenkins test results: PENDING
Thanks,
Robert Levas
