[AMBARI-8336] Add Security State to Ambari database

• Type: New Feature
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: ambari-server
• Labels: kerberos
• Epic Link: Ambari Automated Kerberization
• Assignee: Robert Levas
• Reporter: Robert Levas
• Created: 14/Nov/14 20:16
• Updated: 08/Jan/15 16:08
• Resolved: 24/Nov/14 17:51

Description

In order to track which services and components have been or need to be secured, several tables need to be updated with a security_state column to contain one the following values:

• UNKNOWN - Indicates that it is not known whether the service or component is secured or not
• UNSECURED - Indicates service or component is not or should not be secured
• SECURED_KERBEROS - Indicates component is or should be secured using Kerberos
• SECURING - Indicates the component is in the process of being secured
• UNSECURING - Indicates the component is in the process of being unsecured
• ERROR - Indicates the component is not secured due to an error condition

The following tables need to be updated:

• hostcomponentdesiredstate - To indicate whether the component needs security added or removed
• hostcomponentstate - To indicate whether the component is currently configured for security or not
• servicedesiredstate - To indicate whether the service (and it components) should or should not be secured

Issue Links

• is depended upon by: AMBARI-9045 Capture security state from components for use in enabling or disabling Kerberos
• is required by: AMBARI-8343 Components should indicate Security State (via ambari-agent)
• is required by: AMBARI-7449 Update API to enable configuring of services to use Kerberos
• links to: ReviewBoard