[
https://issues.apache.org/jira/browse/AMBARI-15373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-15373:
----------------------------------
Description:
Provide an entry point in the REST API to retrieve the _composite_ Kerberos
descriptor. This includes the default Kerberos descriptor built from the stack
definitions overlaid with the (potentially sparse) Kerberos descriptor stored
as an artifact of the cluster.
The entry point should be a read-only sub-resource of "clusters", and should
only be made available if asked for explicitly due to the size of the data that
will be returned.
{noformat:title=Example API call}
GET /api/v1/clusters/:cluster_name/kerberos_descriptors/COMPOSITE
{noformat}
Note: Kerberos Descriptors available via this interface are:
* STACK - the default Kerberos Descriptor from the relevant stack definition
* USER - the user-suppled updates to the stack default Kerberos Descriptor
* COMPOSITE - the stack default Kerberos Descriptor with the user-suppled
updates applied (this is the Kerberos Descriptor used when performing
Kerberos-related operations)
was:
Provide an entry point in the REST API to retrieve the _composite_ Kerberos
descriptor. This includes the default Kerberos descriptor built from the stack
definitions overlaid with the (potentially sparse) Kerberos descriptor stored
as an artifact of the cluster.
The entry point should be a read-only sub-resource of "clusters", and should
only be made available if asked for explicitly due to the size of the data that
will be returned.
{noformat:title=Example API call}
GET /api/v1/clusters/:cluster_name/kerberos_descriptor
{noformat}
> Provide composite Kerberos Descriptor via the REST API
> ------------------------------------------------------
>
> Key: AMBARI-15373
> URL: https://issues.apache.org/jira/browse/AMBARI-15373
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: kerberos_descriptor, rest_api
> Fix For: 2.4.0
>
>
> Provide an entry point in the REST API to retrieve the _composite_ Kerberos
> descriptor. This includes the default Kerberos descriptor built from the
> stack definitions overlaid with the (potentially sparse) Kerberos descriptor
> stored as an artifact of the cluster.
> The entry point should be a read-only sub-resource of "clusters", and should
> only be made available if asked for explicitly due to the size of the data
> that will be returned.
> {noformat:title=Example API call}
> GET /api/v1/clusters/:cluster_name/kerberos_descriptors/COMPOSITE
> {noformat}
> Note: Kerberos Descriptors available via this interface are:
> * STACK - the default Kerberos Descriptor from the relevant stack definition
> * USER - the user-suppled updates to the stack default Kerberos Descriptor
> * COMPOSITE - the stack default Kerberos Descriptor with the user-suppled
> updates applied (this is the Kerberos Descriptor used when performing
> Kerberos-related operations)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
