[
https://issues.apache.org/jira/browse/AMBARI-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364932#comment-14364932
]
Hudson commented on AMBARI-10094:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2053 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2053/])
AMBARI-10094 Kerberos: disable edit on generated ambari principal and keytab
configs. (atkach) (atkach:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=de3667a2195fd7796bc5a9cbc4f7a79d945979b9)
* ambari-web/app/data/HDP2/site_properties.js
> Kerberos: disable edit on generated ambari principal and keytab configs
> -----------------------------------------------------------------------
>
> Key: AMBARI-10094
> URL: https://issues.apache.org/jira/browse/AMBARI-10094
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10094.patch, principal_names.tiff
>
>
> After enabling kerberos, if you browse to Service > Configs, you are see
> properties for Ambari Principals *_principal_name. For example,
> smokeuser_principal_name can be seen in all services, and
> hbase_principal_name can be see in HBase.
> Attached screen shot shows the properties showing thru the Service > Hbase >
> Configs tab.
> There properties should not be editable by the user in the UI. These values
> are generated by the kerb infra based on the descriptor pattern, and a user
> editing these can cause issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
