You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nahappan Somasundaram (JIRA)" <ji...@apache.org> on 2016/10/24 23:01:05 UTC
[jira] [Updated] (AMBARI-18687) Ambari-agent: CLI utility to
support storing passwords using hadoop credential store
[ https://issues.apache.org/jira/browse/AMBARI-18687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nahappan Somasundaram updated AMBARI-18687:
-------------------------------------------
Summary: Ambari-agent: CLI utility to support storing passwords using hadoop credential store (was: Ambari-agent: Support storing passwords using hadoop credential store)
> Ambari-agent: CLI utility to support storing passwords using hadoop credential store
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-18687
> URL: https://issues.apache.org/jira/browse/AMBARI-18687
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
> Affects Versions: 2.4.2
> Reporter: Nahappan Somasundaram
> Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
>
> Some components support the use of Hadoop Credential Store API to read passwords from a JCEKS provider. If this is enabled, ambari agent must be able to use the JCEKS provider to store passwords.
> This requires writing a command line wrapper utility over the Hadoop Credential Provider API in Java on the ambari agent side. Whenever a non-status command is received, ambari agent will use this utility to create the JCEKS provider for each configuration with the passwords in them.
> After that, the configuration XML files will be generated using the path to their respective JCEKS provider path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)