[
https://issues.apache.org/jira/browse/AMBARI-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234762#comment-14234762
]
Rishi Pidva commented on AMBARI-8166:
-------------------------------------
[~rlevas], [~bergenholtz], As per my understanding, Oozie check in agent is not
REST API based. I believe we mean the same for KDC as well. Since the cluster
hosts need to directly connect to KDC, the check will be between them.
For Ambari Server, we'll have a REST API between client and server to validate
KDC Admin credentials. Please correct me if anything is not accurate.
> Implement custom command for checking connectivity to KDC, via REST API
> -----------------------------------------------------------------------
>
> Key: AMBARI-8166
> URL: https://issues.apache.org/jira/browse/AMBARI-8166
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-agent, ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Rishi Pidva
> Labels: connectivity_, kdc, kerberos
>
> There needs to be a way, given the details about a KDC to verify that Ambari
> and (optionally) the nodes in the existing cluster can connect to it.
> From the cluster hosts, this test should test that the address and port
> combinations are reachable.
> From the Ambari server, this test should make sure the administrator
> credentials allow at least read access to the KDC.
> As an example of a similar action, see how Oozie does this for DB check pre
> install.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
