You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "JaySenSharma (JIRA)" <ji...@apache.org> on 2018/07/27 05:24:00 UTC

[jira] [Updated] (AMBARI-24368) Manage different keystore passwords for different hosts inside the "ssl-server.xml" should work via config-group option.

     [ https://issues.apache.org/jira/browse/AMBARI-24368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

JaySenSharma updated AMBARI-24368:
----------------------------------
    Affects Version/s: 2.6.2

> Manage different keystore passwords for different hosts inside the "ssl-server.xml"  should work via config-group option.
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-24368
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24368
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.6.2, 2.7.0
>         Environment: All
>            Reporter: JaySenSharma
>            Priority: Major
>
> -  When "ssl-server.xml" and "ssl-client.xml" files are being managed by Ambari., users can set only one password for the keystore defined for every host.
> -  Even when user try using the "Config Group" option then they see that it allows them to have different configs for "ssl.server.keystore.location" but config group option does not allow to override the "ssl.server.keystore.keypassword" value for different config groups.
> - Ideally in ambari ui similar to the override option for "ssl.server.keystore.location" user should also be able to override "ssl.server.keystore.keypassword" (truststore password) options so that every host can have different set of keystore and passwords?
> Similarly for other configs like /HDFS/YARN/Spark SSL configurations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)