Appendix C. LDAP URLs
Appendix C. LDAP URLs LDAP URLs identify the Red Hat Directory Server instance, similarly to the way site URLs identify a specific website or web page. There are three common times when the LDAP URL of the Directory Server instance is used: The LDAP URL is used to identify the specific Directory Server instance when the Directory Server is accessed using a web-based client. LDAP URLs are used to configure Directory Server referrals. LDAP URLs are used to configure access control instructions. Note The LDAP URL format is described in RFC 4516, which is available at http://www.ietf.org/rfc/rfc4516.txt . C.1. Components of an LDAP URL It is also possible to use IPv4 or IPv6 addresses instead of the host name. The ldap:// protocol is used to connect to LDAP servers over unsecured connections, and the ldaps:// protocol is used to connect to LDAP servers over TLS connections. Table C.1, "LDAP URL Components" lists the components of an LDAP URL. Note The LDAP URL format is described in RFC 4516, which is available at http://www.ietf.org/rfc/rfc4516.txt . Table C.1. LDAP URL Components Component Description host name Name, IPv4, o r IPv6 address of the LDAP server. For example, ldap.example.com , 192.0.2.90 , or [2001:db8::1]. port Port number of the LDAP server (for example, 696 ). If no port is specified, the standard LDAP port ( 389 ) or LDAPS port ( 636 ) is used. base_dn Distinguished name (DN) of an entry in the directory. This DN identifies the entry that is the starting point of the search. If no base DN is specified, the search starts at the root of the directory tree. attributes The attributes to be returned. To specify more than one attribute, use commas to separate the attributes; for example, cn,mail,telephoneNumber . If no attributes are specified in the URL, all attributes are returned. scope The scope of the search, which can be one of these values: base retrieves information only about the distinguished name ( base_dn ) specified in the URL. one retrieves information about entries one level below the distinguished name ( base_dn ) specified in the URL. The base entry is not included in this scope. sub retrieves information about entries at all levels below the distinguished name ( base_dn ) specified in the URL. The base entry is included in this scope. If no scope is specified, the server performs a base search. filter Search filter to apply to entries within the specified scope of the search. If no filter is specified, the server uses the filter (objectClass=*) . The attributes, scope, and filter components are identified by their positions in the URL. Even if no attributes are specified, the question marks still must be included to delimit that field. For example, to specify a subtree search starting from dc=example,dc=com that returns all attributes for entries matching (sn=Jensen) , use the following LDAP URL: The two consecutive question marks, ?? , indicate that no attributes have been specified. Since no specific attributes are identified in the URL, all attributes are returned in the search.
ldap[s]:// hostname:port/base_dn?attributes?scope?filter ldap://ldap.example.com/dc=example,dc=com??sub?(sn=Jensen)