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.
Description of problem:
The webui does not feature the ability to select LDAP authentication for users accounts. This is a "must have" feature for a companies that requires things such as PCI DSS compliance (all userIDs must be unique, which requires integration to for example a LDAP service).
Version-Release number of selected component (if applicable):
Katello 1.4.8-1.git.4.c940d43.el6
How reproducible:
N/A
Steps to Reproduce:
Add a new user: Administer > Users > Add new user.
Actual results:
Create a new user, there are no options to select a LDAP authentication source.
Expected results:
Option to select a LDAP authentication source when adding new users.
Additional info:
This is a blocker for companies that requires for example PCI DSS compliance.
moved this to our downstream product to align to a future release.
moving to severity high as Urgent is reserved for "we have 24 hours to resolve this issue" type bugs where *nothing* is functional.