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.
Description of problem:
In RHEL 6 (and earlier), if you had multiple applications using pam-ldap and each application was authenticating against different ldap servers (with unique binddn accounts, search bases, urls, etc.) you could point the application to a file in /etc/pam.d/. In that file inside /etc/pam.d/ you could have a line like the following:
auth required pam_ldap.so config=/etc/ldap.conf.d/ldapconfig1.conf
The next application could have its own file in pam.d with a line like:
auth required pam_ldap.so config=/etc/ldap.conf.d/ldapconfig2.conf
etc.
This allowed each application to have completely different ldap configurations.
Now, it appears that in RHEL 7, all of this information must exist in a single configuration file: /etc/nslcd.conf. This prevents the ability to use multiple configurations. Is there another way to accomplish the setup that was allowed in RHEL 6 and earlier?
If I create a file in /etc/pam.d like this:
auth required pam_ldap.so config=/etc/ldap.conf.d/ldapconfig1.conf
I will get the following error in /var/log/secure:
"unknown option: config=/etc/ldap.conf.d/ldapconfig1.conf"
Version-Release number of selected component (if applicable): 0.8.13
How reproducible:
Create the config option line on a RHEL 7 server, similar to this:
auth required pam_ldap.so config=/etc/ldap.conf.d/ldapconfig1.conf
There doesn't appear to be a way to have multiple ldap configurations in nslcd.conf and the "config" option line appears to have been removed.
Steps to Reproduce:
1. Try to use "config=" argument in a pam ldap file in /etc/pam.d/
2. Try to use multple ldap configs in /etc/nslcd.conf
Actual results:
"unknown option: config=/etc/ldap.conf.d/ldapconfig1.conf"
Expected results:
There should be a way to use multiple ldap authentication configurations on a single server.
Additional info:
Yes, I'm sorry, but this is simply not possible because in RHEL-7 the pam_ldap module is just a thin wrapper that talks to the nslcd deamon which is a singleton with a single configuration..