https://bugs.openldap.org/show_bug.cgi?id=9317
Issue ID: 9317 Summary: LDAPS connection fails to multi-IP DNS using DIGEST-MD5 mechanism Product: OpenLDAP Version: 2.4.46 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: libraries Assignee: bugs@openldap.org Reporter: paul.raines@gmail.com Target Milestone: ---
Our MS AD ldap servers are in DNS using alias ldap.example.org at multiple IP addresses like so:
# host ldap.example.org ldap.example.org has address 172.18.1.10 ldap.example.org has address 172.21.1.10 ldap.example.org has address 172.24.1.10 ldap.example.org has address 172.30.1.10
For CentOS 6 this was not a problem. But with CentOS 7 (2.4.44) and CentOS 8 (2.4.46) the following fails
# ldapwhoami -d -1 -H ldaps://ldap.example.org -Y DIGEST-MD5 -U username -W
with the error:
ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: 80090303: LdapErr: DSID-0C090574, comment: The digest-uri does not match any LDAP SPN's registered for this server., data 0, v3839 ldap_free_connection 1 1 ldap_send_unbind
If one reverse DNS IP lookups one of the IPs and uses the unique name (e.g. ldap01.example.org) instead it works fine
I think openldap should work in this case with DNS aliases.
https://bugs.openldap.org/show_bug.cgi?id=9317
--- Comment #1 from Quanah Gibson-Mount quanah@openldap.org --- Hello,
I believe you'll need to consult with RedHat on this issue, as this appears related to changes they've made to the OpenLDAP software that are not from the OpenLDAP project itself. I would suggest filing a bug in their bugzilla.
Regards, Quanah
https://bugs.openldap.org/show_bug.cgi?id=9317
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
https://bugs.openldap.org/show_bug.cgi?id=9317
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED