(ITS#8848) New LDAP URL syntax to support binding to specific IP address at client side

[sudhir.singam@nokia.com]

Full_Name: Singam Sudhir Reddy
Version: master branch
OS: fedora
URL: ftp://ftp.openldap.org/incoming/sudhirsingam-180505.patch
Submission from: (NULL) (131.228.66.13)


The attached file is derived from OpenLDAP Software. All of the modifications to
OpenLDAP Software represented in the following patch(es) were developed by
NOKIA. NOKIA has not assigned rights and/or interest in this work to any party.
I, SINGAM SUDHIR REDDY authorized by NOKIA, my employer, to release this work
under the following terms.

NOKIA hereby place the following modifications to OpenLDAP Software (and only
these modifications) into the public domain. Hence, these modifications may be
freely used and/or redistributed for any purpose with or without attribution
and/or other notice.

****

Description:

Currently when using the openldap client and try to connect to LDAP server using
LDAP URL, client automatically binds to an IP address returned by kernel.

For example, in the below usage, client automatically binds to an IP address
returned by kernel.

ldapsearch -H ldap://10.63.57.239:389 D "uid=admin, ou=administrators,
ou=topologymanagement, o=netscaperoot" -x -w admin -b "uid=baha, ou=people,
ou=accounts, ou=region-911080, ou=regions, ou=netact, dc=noklab, dc=net,
dc=localdomain"

But if we want to route the traffic on a specific interface/IP address,
currently there is no provision. And the idea or enhancement is to introduce
such provision by giving source bind IP address in the URL in the following
format.

ldap://TARGET-IP-ADDRESS@SOURCE-BIND-IP-ADDRESS:PORT

For example,

ldapsearch -H ldap://10.63.57.239@10.37.220.9:389 D "uid=admin,
ou=administrators, ou=topologymanagement, o=netscaperoot" -x -w admin -b
"uid=baha, ou=people, ou=accounts, ou=region-911080, ou=regions, ou=netact,
dc=noklab, dc=net, dc=localdomain"

Note this feature is backward compatible, that is, it is optional to provide
source bind IP address in the URL.

This feature also supports IPV6 addresses.