[
https://issues.apache.org/jira/browse/AMBARI-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234850#comment-14234850
]
Jaimin D Jetly commented on AMBARI-8166:
----------------------------------------
We need to test that the KDC host:port are reachable from all hosts in the
cluster as part of this task. It will be a pre-check before installing kerberos
clients on all hosts and configuring kerberos client related files (krb5.conf).
Authentication of an identity (smokeuser identity) will be done after kerberos
service (comprises of only kerberos client components) is installed as part of
kerberos service check command (smoke test for kerberos service). This will be
a separate task.
> 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
> Attachments: Screen Shot 2014-11-04 at 11.16.41 PM.png
>
>
> 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)
