[
https://issues.apache.org/jira/browse/AMBARI-10096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364387#comment-14364387
]
Hudson commented on AMBARI-10096:
---------------------------------
ABORTED: Integrated in Ambari-branch-2.0.0 #87 (See
[https://builds.apache.org/job/Ambari-branch-2.0.0/87/])
AMBARI-10096. Kerberos: expose AD config properties in service > configs.
(jaimin) (jaimin:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e796be667eb7dec4ebd2e3e0ff52e23c26ab586f)
* ambari-web/app/utils/config.js
* ambari-web/app/data/HDP2/site_properties.js
> Kerberos: expose AD config properties in service > configs
> ----------------------------------------------------------
>
> Key: AMBARI-10096
> URL: https://issues.apache.org/jira/browse/AMBARI-10096
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-10096.patch, AMBARI-10096.patch.2,
> AMBARI-10096_2.0.0.patch
>
>
> In Services > Kerberos > Configs UI after setting up Kerb, need to:
> - In case of AD, expose LDAP (ldap_url) and DN (container_dn). Currently,
> these are not exposed so user cannot modify if they need to post-enable
> Kerberos.
> - In case of AD or MIT, "Realm name" should not be editable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
