Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Bug 1552632

Summary:	[RFE] Creating a new user with LDAP, password field should be disabled or grayed out.
Product:	Red Hat Satellite	Reporter:	Shivdutt Bharadwaj <shbharad>
Component:	Users & Roles	Assignee:	Marek Hulan <mhulan>
Status:	CLOSED ERRATA	QA Contact:	Sanket Jagtap <sjagtap>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.12	CC:	bkearney, dchaudha, dhlavacd, mhulan, sjagtap
Target Milestone:	6.4.0	Keywords:	FutureFeature, Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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 15:30:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shivdutt Bharadwaj 2018-03-07 13:14:29 UTC

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 10:24:42 UTC

Created redmine issue http://projects.theforeman.org/issues/23347 from this bug

Comment 4 Satellite Program 2018-04-20 12:16:34 UTC

Upstream bug assigned to mhulan

Comment 5 Satellite Program 2018-04-20 12:16:37 UTC

Upstream bug assigned to mhulan

Comment 6 Satellite Program 2018-04-22 12:16:28 UTC

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 15:25:48 UTC

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


PFA

Comment 10 Marek Hulan 2018-09-11 15:46:16 UTC

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 16:01:40 UTC

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 11:41:02 UTC

Yes, the bug I filed is closed as duplicate.

Comment 15 errata-xmlrpc 2018-10-16 15:30:28 UTC

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