Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a new users choosing LDAP on satellite through CLI 
2. A password should be passed even if it is unnecessary as it won't be used 
Satellite cannot write to ldap

 hammer user create --auth-source-id 3 --firstname foobar --login foobar --mail 'foobar' --roles 'Viewer'
Could not create the user:
  Missing arguments for 'user[password]'
[root@qe-testing-rhel7 ~]# hammer user create --auth-source-id 3 --firstname foobar --login foobar --mail 'foobar' --roles 'Viewer' --password apple
User [foobar] created.

Actual results:
If auth-source is specified , user still need to add password to create user 

Expected results:
When auth-source is specified user should not need to add password to create user

Additional info:

Martin, is this easily doable in hammer and does it fit to how hammer works? Basically the option would be optional and only required when auth source is internal.

Sanket, would you be fine with keeping the --pasword option but make it optional? We'd just mention in documentation it's required for internal auth sources.

Yes, password should be optional for the auth sources that are external , and user should be created without specifying it.

Seems it was already reported, closing as dup

*** This bug has been marked as a duplicate of bug 1561691 ***

I prefer to have this fixed on the API side. The original bug has proper fix in API doc.