You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/02/06 16:11:00 UTC
[jira] [Commented] (AMBARI-22910) Add Ambari admin/pw CLI options
for setup-ldap tool
[ https://issues.apache.org/jira/browse/AMBARI-22910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354075#comment-16354075 ]
Hudson commented on AMBARI-22910:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8683 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8683/])
[AMBARI-22910] Add Ambari admin/pw CLI options for setup-ldap tool (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=7ee8c6177a412875c0712df991a19aec1c73515d])
* (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
> Add Ambari admin/pw CLI options for setup-ldap tool
> ---------------------------------------------------
>
> Key: AMBARI-22910
> URL: https://issues.apache.org/jira/browse/AMBARI-22910
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 2.7.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Labels: ldap, pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Since we use Amabri's REST API in the _setup-ldap_ tool to persists its outcome into the DB we require the end-user to type his/her Ambari username and password during the user input phase.
> This makes automated integration tests very hard to implement.
> The solution is to add two new CLI option names for _setup-ldap_ (similarly to the _sync-ldap_ tool):
> {code:java}
> --ldap-setup-admin-name
> --ldap-setup-admin-password{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)