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

Andrii Babiichuk updated AMBARI-8886:
-------------------------------------
    Attachment: AMBARI-8886.patch

> Add Service wizard: Show identities and secure configuration for new services
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-8886
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8886
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8886.patch
>
>
> If a cluster is secured (Kerberos service is installed and 
> cluster-env/security_enabled flag is true) then a new page "Configure 
> Identities" should be shown after "Customize Service Configurations" page and 
> before "Review page" on Add Service Wizard.
> # Before landing on this page, kerberos descriptor will be fetched from 
> clusters resource (api/v1/clusters/c1?fields=kerberos_descriptor). For now 
> mock this call
> # This new page *Configure Identities* on *Add Service Wizard* should be 
> similar to the *Configure Identities* page displayed on *Enable Kerberos 
> Wizard*.
> # Properties related to the stack level identities and properties related to 
> the identities of the installed services should be non-editable fields. 
> Properties related to the identities of the newly installed services should 
> be editable.
> # Also show the fields for Admin principal and Admin password (empty by 
> default) on this page in general section. 
> *Note:*  Updating the cluster with the kerberos descriptor and the session 
> attributes with the admin credentials will be done in a separate task. 
> This work should be visible only if automatedKerberos experimental flag is 
> set to true.



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

Reply via email to