Member since
09-10-2015
12
Posts
2
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2888 | 01-19-2016 06:20 PM |
01-19-2016
06:31 PM
Thanks for closing the thread. @Erik Nor
... View more
12-15-2015
06:50 PM
1 Kudo
It appears that the UI stores the realm in the user-specified Kerberos descriptor artifact and that at some point the lowercase form of the realm was specified. However when the case of the realm was corrected, the user-specified Kerberos descriptor artifact was not updated and therefore the test Kerberos identity was created incorrectly. I think this would have corrected itself if the test was skipped, but rather than take a chance on that, it is best to back out of the Kerberos Wizard (to the first page of it) and then exit - this makes sure the Kerberos service is cleaned up properly. Then the user-specified Kerberos descriptor artifact needs to be deleted using DELETE /api/v1/clusters/CLUSTER_NAME/artifacts/kerberos_descriptor Note: replace CLUSTER_NAME with the name of the cluster. For example: curl -H "X-Requested-By:ambari" -u admin:admin -i -X DELETE http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/artifacts/kerberos_descriptor Then restart the Enable Kerberos Wizard, making sure to set the realm with the proper case.
... View more