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:
Can not select multiple LDAP servers with authconfig
Version-Release number of selected component (if applicable):
authconfig-6.2.8-8.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
[root@dhcp210-38 ~]# authconfig --enableldap --enableldapauth --ldapserver='ldap://ldap1.example.com ldap://ldap2.example.com ldap://ldap3.example.com' --ldapbasedn="dc=example,dc=com" --update
authconfig: Invalid LDAP URI.
Job for nslcd.service failed. See 'systemctl status nslcd.service' and 'journalctl -xn' for details.
[root@dhcp210-38 ~]# authconfig --enableldap --enableldapauth --ldapserver='ldap://ldap1.example.com,ldap://ldap2.example.com,ldap://ldap3.example.com' --ldapbasedn="dc=example,dc=com" --update
authconfig: Invalid LDAP URI.
Job for nslcd.service failed. See 'systemctl status nslcd.service' and 'journalctl -xn' for details.
Actual results:
Authconfig now takes only one LDAP server in arguement.
Expected results:
authconfig should take multiple server in arguement.
nslcd.conf man page says following about multiple uri:
This option may be specified multiple times. Normally, only the first server will be used with the following servers as fallback (see bind_timelimit below).
We should simply add 3 uri entries to nslcd.conf
This option may also influence sssd.conf.
sssd may also take multiple ldap uris but it has different syntax. It takes comma-separated list of URIs.
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.
https://rhn.redhat.com/errata/RHBA-2015-0512.html
I am using centos 7 and the bug seems to persist when I use:
authconfig --ldapserver="ldap://simple-provider.example.com,ldap://clone-provider.example.com"
Which ever I put first will be the ldap server and switching off that server will not change the ldap server. I am using virtual box to create the servers and clients