Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.1.0
Description
If I go through setup of secure cluster, also execute ambari-server setup-security option #3, there are 2 problems:
- Ambari does not kinit using the specified principal and keytab
- If I manually kinit, all is well until the ticket expires - I would expect Ambari to renew ticket prior to expiry.
- The process uses the interactive user's ticket cache (separate Jira:
AMBARI-11001)
Attachments
Issue Links
- is blocked by
-
AMBARI-11001 Ambari uses users' interactive ticket cache
- Resolved