[AMBARI-10305] Kerberos: during disable, need option skip if unable to access KDC to remove principals

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: ambari-server
• Labels: kerberos
• Assignee: Robert Levas
• Reporter: Robert Levas
• Created: 01/Apr/15 00:35
• Updated: 14/Apr/15 18:47
• Resolved: 10/Apr/15 16:53

Description

Attempted to disable kerb, fails on step to unkerberize because KDC admin is locked out.

Click retry, can't make it past that.

Need option to skip and finish "disable kerberos" even if Ambari cannot get the principals cleaned up (i.e. cannot access the KDC) Losing access to the KDC and attempting to disable where ambari can't clean-up the principals should be a skip'able step. User should still be able to get to a clean, not-enabled-kerberos-ambari-state w/o accessing the KDC.

Solution
Add a flag to the kerberos-env configuration to specify whether Kerberos identities should be managed by Ambari (true, default) or not (false). This flag is to be overridable via a directive like manage_identities=false when disabling Kerberos, which will skip over any KDC administrative processes.

Issue Links

• relates to: AMBARI-10479 Add the ability to enable Kerberos and not manage identities
• links to: ReviewBoard