Hudson commented on AMBARI-18888:

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6132 (See 
AMBARI-18888: Ambari-agent: Create configuration files with JCEKS 
* (edit) ambari-agent/src/packages/tarball/all.xml
* (edit) 
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit) ambari-agent/conf/unix/ambari-agent.ini
* (edit) 
* (edit) 

> Ambari-agent: Create configuration files with JCEKS information
> ---------------------------------------------------------------
>                 Key: AMBARI-18888
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18888
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-agent
>            Reporter: Nahappan Somasundaram
>            Assignee: Nahappan Somasundaram
>         Attachments: rb53747.patch
> When a non-status command is received, a command.json file is generated. This 
> file contains the passwords used in a configuration. When the command is then 
> executed, ambari agent spawns off a subprocess to execute component-specific 
> Python scripts to generate the configuration files using the data from the 
> command.json file.
> To avoid storing clear text passwords in command.json file and configuration 
> files, ambari-agent will first generate the JCEKS files corresponding to the 
> configuration information in the command JSON blob coming from the server and 
> then generate the command.json with the path to the JCEKS store instead of 
> clear text passwords for *password* properties.
> Subsequently when executing a command, ambari-agent will generate the 
> configuration files with the JCEKS path information from command.json.

This message was sent by Atlassian JIRA

Reply via email to