[
https://issues.apache.org/jira/browse/AMBARI-19915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-19915:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5:
[481cfe56ec839d2225ecdaf2f778f13d031223ad|https://github.com/apache/ambari/commit/481cfe56ec839d2225ecdaf2f778f13d031223ad]
and trunk:
[b5014253706c85cba77c781672443d94de3e5ef4|https://github.com/apache/ambari/commit/b5014253706c85cba77c781672443d94de3e5ef4]
> Add Ranger KMS SSL properties in ambari stack
> ---------------------------------------------
>
> Key: AMBARI-19915
> URL: https://issues.apache.org/jira/browse/AMBARI-19915
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Mugdha Varadkar
> Assignee: Mugdha Varadkar
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19915.1.patch, AMBARI-19915.patch
>
>
> These are few properties, we observed in Ranger KMS: which needs to be added
> in Ambari for Ranger KMS in SSL environment.
> * ranger.service.https.attrib.keystore.file
> * ranger.service.https.attrib.client.auth
> * ranger.service.https.attrib.keystore.keyalias
> * ranger.service.https.attrib.keystore.pass
> * ranger.credential.provider.path
> * ranger.service.https.attrib.keystore.credential.alias
> Along with addition of these properties, we need to mask password properties
> so that plaintext passwords are not visible in config files.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
