AMBARI-23026. Using smoke user's principal/keytab within alerts in a secure cluster

[smolnar82]

What changes were proposed in this pull request?

All types of alerts should use Ambari's smoke user principal and keytab to authenticate a service when triggering an alert.

How was this patch tested?

Executing unit tests in ambari-server.

E2E tests:

1. installed a secure cluster with the services I changed the alert definitions for
2. copied the new alert definitions with my changes
3. restarted the server and the agents
4. checked some of the alerts in question: they we all ok; not authentication error occurred

[asfgit]

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3847/
Test PASSed.

[rlevas]

Did you ensure that the relevant kerberos.json files indicate that the Ambari smoke test user's Kerberos identity is distributed to the hosts where the service's components are installed?

[rlevas]

For example the kerberos.json file at common-services/HDFS/2.1.0.2.0/kerberos.json contains the following...

{
  "services": [
    {
      "name": "HDFS",
      "identities": [
        ...,
        {
          "name": "hdfs_smokeuser",
          "reference": "/smokeuser"
        }
      ],
      ...

This indicates the the smoke user's keytab file will be distributed to all hosts where a component of HDFS is installed.

[smolnar82]

@rlevas
No, I have not done such a check; let me do it and update the Kerberos descriptor(s) if needed. I'll keep you posted (or will push a new commit to this PR).

[smolnar82]

@rlevas
I checked the Kerberos descriptors of all services that I've changed in this PR and found that all have their own SERVICENAME_smokeuser identity in place.
Thanks for your comment; it was very useful for me for the future.