Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
DescriptionMatthew Harmsen
2021-10-23 16:17:05 UTC
he following issue was reported by awnuk:
Current directory authentication plugin works in two steps:
it verifies ability to connect to the directory
it retrieves password from user entry to compare it against password provided by user during enrollment
Unfortunately in both steps, the directory authentication plugin is using directory admin password.
It is also not the best security wise solution to retrieve a user's password just for comparison.
If you would like to preserve two steps approach, then it would be better to
anonymously access RootDSE in directory (to verify ability to connect to the directory or ignore this step)
verify if plugin can authenticate as a user, with credential provided during the enrollment (additionally plugin could check user's membership attribute or specified attribute)
This way you could avoid storing (in CS.cfg) and using directory admin credentials and retrieving user credentials.
ajwnuk added a commit to ajwnuk/pki that referenced this issue 4 days ago
Authentication issue dogtagpki#3629
d262b43
ajwnuk mentioned this issue 4 days ago
Authentication issue #3629 #3787
Merged
jmagne pushed a commit that referenced this issue 2 days ago
Authentication issue #3629 (#3787)
cf3fb92
Co-authored-by: Andrew Wnuk <awnuk>
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 (pki-core bug fix and enhancement update), 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/RHBA-2021:4791
he following issue was reported by awnuk: Current directory authentication plugin works in two steps: it verifies ability to connect to the directory it retrieves password from user entry to compare it against password provided by user during enrollment Unfortunately in both steps, the directory authentication plugin is using directory admin password. It is also not the best security wise solution to retrieve a user's password just for comparison. If you would like to preserve two steps approach, then it would be better to anonymously access RootDSE in directory (to verify ability to connect to the directory or ignore this step) verify if plugin can authenticate as a user, with credential provided during the enrollment (additionally plugin could check user's membership attribute or specified attribute) This way you could avoid storing (in CS.cfg) and using directory admin credentials and retrieving user credentials.