[AMBARI-8899] Knox service components should indicate security state

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: ambari-agent, stacks
• Labels: kerberos
• Epic Link: Ambari Automated Kerberization
• Assignee: Robert Levas
• Reporter: Robert Levas
• Created: 23/Dec/14 21:17
• Updated: 07/Jan/15 03:47
• Resolved: 07/Jan/15 02:09

Description

The Knox service components should indicate security state when queried by Ambari Agent via STATUS_COMMAND. Each component should determine it's state as follows:

KNOX_GATEWAY

Indicators

• Command JSON
  • config['configurations']['cluster-env']['security_enabled']
    • = “true”
• Configuration File: knox_conf_dir + '/krb5JAASLogin.conf'
  • keyTab
    • not empty
    • path exists and is readable
    • required
  • principal
    • not empty
    • required

Pseudocode

if indicators imply security is on and validate
    if kinit(principal) succeeds
        state = SECURED_KERBEROS
    else
        state = ERROR 
else
    state = UNSECURED

Note: Due to the cost of calling kinit results should be cached for a period of time before retrying. This may be an issue depending on the frequency of the heartbeat timeout.
Note: kinit calls should specify a temporary cache file which should be destroyed after command is executed - BUG-29477

Issue Links

• links to: ReviewBoard