Support LDAP server discovery via DNS SRV records
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
When an organization has more than one LDAP server and a potentially large number of clients connecting to them, they may support automatic discovery of those servers by creating DNS SRV records for them. The overview of how this works is described here:
http://
When using OpenLDAP utilities like the ldapsearch command line tool, we can use syntax like this to discover an LDAP host and make queries against it:
ldapsearch -H ldap://
python-ldap does not support discovery this way. It interprets a URL like this as referring to a file on localhost. Based on this thread, it seems unlikely that python-ldap or libldap would be willing to support this:
https:/
Their concerns seem to be about this being a major change in behavior. It also poses a problem for TLS-secured hosts since we'd no longer be requesting the host directly by its CN, also mentioned in this thread:
http://
We could implement this in keystone, as a wrapper around ldappool/
It looks like RedHat has had this idea as well:
https:/
In that report, Nathan suggests that this should be in python-ldap rather than keystone, but based on the above python-ldap thread I think that might be an uphill battle.
Thoughts?
Changed in keystone: | |
status: | New → Triaged |
tags: | added: foobar |
tags: | removed: foobar |
This certainly sounds like it would be useful. I'd be curious to see what operators or users bite on this. Do you know who that would be?