Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1552632 - [RFE] Creating a new user with LDAP, password field should be disabled or grayed out.
[RFE] Creating a new user with LDAP, password field should be disabled or gra...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Users & Roles (Show other bugs)
6.2.12
Unspecified Unspecified
unspecified Severity medium (vote)
: GA
: Unused
Assigned To: Marek Hulan
Sanket Jagtap
: FutureFeature, Triaged, UserExperience
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-07 08:14 EST by Shivdutt Bharadwaj
Modified: 2018-10-16 11:31 EDT (History)
5 users (show)

See Also:
Fixed In Version: foreman-1.18.0.0.2-1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-16 11:30:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 23347 None None None 2018-04-20 06:24 EDT
Red Hat Product Errata RHSA-2018:2927 None None None 2018-10-16 11:31 EDT

  None (edit)
Description Shivdutt Bharadwaj 2018-03-07 08:14:29 EST
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):
6.2.x

How reproducible:


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.
3. 

Actual results:
Password field is there in new user form when LDAP is chosen.

Expected results:
No password field. 

Additional info:
Comment 2 Marek Hulan 2018-04-20 06:24:42 EDT
Created redmine issue http://projects.theforeman.org/issues/23347 from this bug
Comment 4 pm-sat@redhat.com 2018-04-20 08:16:34 EDT
Upstream bug assigned to mhulan@redhat.com
Comment 5 pm-sat@redhat.com 2018-04-20 08:16:37 EDT
Upstream bug assigned to mhulan@redhat.com
Comment 6 pm-sat@redhat.com 2018-04-22 08:16:28 EDT
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23347 has been resolved.
Comment 9 Sanket Jagtap 2018-09-11 11:25:48 EDT
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 'foobar@example.com' --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@example.com' --roles 'Viewer' --password apple
User [foobar] created.


PFA
Comment 10 Marek Hulan 2018-09-11 11:46:16 EDT
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.
Comment 11 Sanket Jagtap 2018-09-11 12:01:40 EDT
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
Comment 13 Sanket Jagtap 2018-09-24 07:41:02 EDT
Yes, the bug I filed is closed as duplicate.
Comment 15 errata-xmlrpc 2018-10-16 11:30:28 EDT
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.

https://access.redhat.com/errata/RHSA-2018:2927

Note You need to log in before you can comment on or make changes to this bug.