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:
When trying to use DNS SRV records to set the host option for pam_ldap in RHEL 6, the base option is set to the DNS domainname ignoring any value that's set for base in the pam_ldap.conf file.
Version-Release number of selected component (if applicable):
pam_ldap-185-8.el6
How reproducible:
Very
Steps to Reproduce:
1. Have DNS SRV record for LDAP server
2. Remove host option from pam_ldap.conf and set base option to something other than domain name
3. Enable debugging and see that the base is being set to the domain name
Actual results:
Base is set to the domain name so ldap lookups fail
Expected results:
Base is set to the value in pam_ldap.conf
Additional info:
Might be able to just change _pam_ldap_readconfigfromdns to check whether result->base is NULL before overwriting it
(In reply to comment #0)
> Additional info:
> Might be able to just change _pam_ldap_readconfigfromdns to check whether
> result->base is NULL before overwriting it
The "base" setting in the configuration file is parsed before the configuration is read from DNS, so it should actually be as simple as that.
Nalin, is a patch for this applied in pam_ldap-185-11.el6 applied? I do not see it. Am I wrong? If so, could you point me to it? The latest version of pam_ldap still ignores "base" setting.
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.
http://rhn.redhat.com/errata/RHBA-2011-1701.html