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

Nahappan Somasundaram updated AMBARI-18711:
-------------------------------------------
    Status: Open  (was: Patch Available)

> Ambari-server: DB changes to enable/disable credential store support
> --------------------------------------------------------------------
>
>                 Key: AMBARI-18711
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18711
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.4.2
>            Reporter: Nahappan Somasundaram
>            Assignee: Nahappan Somasundaram
>             Fix For: 2.5.0
>
>
> To enable or disable a component to use credential store, changes are 
> required in the DB to keep track of this information. The 
> _servicedesiredstate_ table can keep track of this information using a new 
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file, 
> then it will specify this information in its stack definition. Services that 
> support using the credential store can be enabled or disabled to use it. 
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has 
> credential store support is provided via the UI and blueprint. This 
> information will then be captured in the _servicedesiredstate_ table in the 
> *credential_store_enabled* column.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to