Description of problem:
When users create a new user with LDAP, password field should be disabled, not allow input, or gray out.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a new users choosing LDAP on satellite 6.2.12.
2. A password/ confirm password field is there which is of no use when users are at LDAP server and cannot write to LDAP Database.
Password field is there in new user form when LDAP is chosen.
No password field.
Created redmine issue http://projects.theforeman.org/issues/23347 from this bug
Upstream bug assigned to email@example.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23347 has been resolved.
Build: Satellite 6.4.0 snap21
User that is created from ldap, has no password field now
This is fixed for the UI , but still lacking in CLI hammer
hammer user create --auth-source-id 3 --firstname foobar --login foobar --mail 'firstname.lastname@example.org' --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 'email@example.com' --roles 'Viewer' --password apple
User [foobar] created.
Sanket, the issue mentioned the UI field only. I don't even think hiding the hammer argument would be helpful, as a user I expect the command line interface to be consistent regardless of what server supports. I you strongly believe it should be hidden in hammer, could you please open this as a separate BZ? There's no need to block this 6.4 BZ because of this IMHO. I believe that should be verified.
One of the ticket that is associated with it, wants the same functionality through hammer.
I would still prefer, this workflow should be similar throughout the CLI adnd UI.
When auth-source is specified don't ask for password
Yes, we can track this separately, will verify this for UI here
Yes, the bug I filed is closed as duplicate.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.