[
https://issues.apache.org/jira/browse/AMBARI-22905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352434#comment-16352434
]
Hudson commented on AMBARI-22905:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8676 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8676/])
AMBARI-22905. Supporting old CLI option names in setup-ldap tool (smolnar:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=05ad34b181db640f7d1540eaa705cee7c93461b3])
* (edit) ambari-server/src/test/python/TestAmbariServer.py
* (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py
* (edit) ambari-server/src/main/python/ambari-server.py
> Support old option names in setup-ldap tool
> -------------------------------------------
>
> Key: AMBARI-22905
> URL: https://issues.apache.org/jira/browse/AMBARI-22905
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> While working on AMBARI-22797 we modified the following option names for the
> setup-ldap tool in AMBARI server:
> # {{ldap-url}} became {{ldap-primary-host}} and {{ldap-primary-port}}
> # {{ldap-secondary-url}} became {{ldap-secondary-host}} and
> {{ldap-secondary-port}}
> To support backward compatibility we need to support old option names too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
