You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2015/11/11 17:15:11 UTC

[jira] [Updated] (AMBARI-13837) Ambari doesn't let user specify Active Directory LDAP configs when using HS2

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

Vitaly Brodetskyi updated AMBARI-13837:
---------------------------------------
    Attachment: AMBARI-13837.patch

> Ambari doesn't let user specify Active Directory LDAP configs when using HS2
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-13837
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13837
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13837.patch
>
>
> HS2 supports LDAP authentication. LDAP could be either Active Directory (AD) or others. For non-AD LDAP, HS2 needs hive.server2.authentication.ldap.url and hive.server2.authentication.ldap.baseDN to be set. For AD LDAP, HS2 needs hive.server2.authentication.ldap.url and hive.server2.authentication.ldap.Domain to be set. However, when using Ambari, when we set hive.server2.authentication to LDAP, it always requires hive.server2.authentication.ldap.baseDN to be set. This prevents users from specifying the AD LDAP configs.



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