Red Hat Bugzilla – Bug 820626
Hide password and email creation fields at user creation time if LDAP auth is enabled in CFSE
Last modified: 2014-11-09 17:56:03 EST
+++ This bug was initially created as a clone of Bug #819002 +++
Description of problem:
When warden is set to ldap the New User option should not be visible as local users are not supported. When a new user is created via the New User option from a LDAP configured instance that user will be unable to login due to the warden value being set to ldap.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure SAM (Katello) with auth type ldap.
2. Login with an administrative user
3. Navigate to the Administrator / Users tab
4. Note the New User option is available
5. Create new user
7. Attempt to login with new user
Unable to login
Either support multiple wardens, r/w access to the ldap to create new users, or disable the new user link when warden is ldap.
--- Additional comment from email@example.com on 2012-05-07 15:07:06 EDT ---
The new user option is still valid under LDAP. Adding a user w/ a valid LDAP username allows you to set additional roles for that user.
It might be worthwhile to remove the ability to set a password for the user, since that password would never get used in LDAP mode
--- Additional comment from firstname.lastname@example.org on 2012-05-08 17:10:26 EDT ---
Changing to RFE to disallow password setting on new user creation in LDAP auth mode
Moving this to severity High:
"Severity Two issues are defined as high-impact issues. The customer's operation is disrupted, but there is some capacity to produce. "
Admins are no longer prompted for email/password when creating LDAP users
However, if for some reason they disable LDAP mode after install (I'm not sure if this is supported or not) those users will not be able to login until a password is set by an admin
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.
getting rid of 6.0.0 version since that doesn't exist