[jira] [Commented] (AMBARI-10096) Kerberos: expose AD config properties in service > configs

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-10096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364190#comment-14364190 ] 

Hadoop QA commented on AMBARI-10096:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12704924/AMBARI-10096.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2057//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2057//console

This message is automatically generated.

> 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
>
>
> 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)