[
https://issues.apache.org/jira/browse/AMBARI-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-8277.
----------------------------------
Resolution: Duplicate
This is really a duplicate of AMBARI-9142. Its the same concept under a
different name.
> Create facility to get and set kerberos plans via REST API
> ----------------------------------------------------------
>
> Key: AMBARI-8277
> URL: https://issues.apache.org/jira/browse/AMBARI-8277
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Blocker
> Labels: api, kerberos, kerberos_plan, resource
> Fix For: 2.0.0
>
>
> To help with _kerberizing_ a cluster, a {{Kerberos Plan}} may be used set
> relevant security properties for a service.
> A {{Kerberos Plan}} is essentially composite {{Kerberos Descriptor}}
> consisting of details for an entire cluster (as opposed to just a single
> service). The details that a Kerberos Plan encapsulates are as follows:
> * Cluster-wide Kerberos Identities
> * Cluster-wide Kerberos-related configurations
> * Service-specific Kerberos Identities
> * Service-specific Kerberos-related configurations
> An (pseudo) Kerberos Plan may be as follows:
> {code}
> {
> "identities": [
> ... cluster-wide identity specifications ...
> ],
> "configurations": [
> ... cluster-wide configuration specifications ...
> ],
> "services": [
> {
> ... service-specific specifications ...
> "components": [
> ... component-specific specifications ...
> ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
