[
https://issues.apache.org/jira/browse/AMBARI-16437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-16437:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 2fcc947530eb521bbcb3bdc941a5a680a4145140
Author: Robert Levas <rle...@hortonworks.com>
Date: Sat May 28 08:02:00 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit ebdbe6f3ec54c09b930bc827fc9aab59c96b90bf
Author: Robert Levas <rle...@hortonworks.com>
Date: Sat May 28 08:18:28 2016 -0400
{noformat}
> Add conditional constraints for Kerberos identities to control when they are
> created
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-16437
> URL: https://issues.apache.org/jira/browse/AMBARI-16437
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Critical
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.4.0
>
> Attachments: AMBARI-16437_trunk_01.patch,
> AMBARI-16437_trunk_02.patch, AMBARI-16437_trunk_03.patch
>
>
> Add conditional constraints for Kerberos identities to control when they are
> created. For example if Kerberos Identity should only be created (and
> distributed) for a component when some other component or service is
> installed.
> An example of this would be
> {code}
> {
> "name": "/HIVE/HIVE_SERVER/hive_server_hive",
> "principal": {
> "configuration":
> "hive-interactive-site/hive.llap.daemon.service.principal"
> },
> "keytab": {
> "configuration": "hive-interactive-site/hive.llap.daemon.keytab.file"
> },
> "when" : {
> "contains" : ["services", "HIVE"]
> }
> }
> {code}
> Note the "{{when}}" clause. This indicates that this identity should only be
> processed when the set of services contains "HIVE". An alternative to this
> would be to test the set of components for a certain component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
