s IMPLEMENTING OPENLDAP in Font

Making QR Code 2d barcode in Font s IMPLEMENTING OPENLDAP

To use one-shot mode, specify the name of the rejection log on the command line as the argument to the -r flag and specify one-shot mode with the -o flag. For example, to process the rejection log file /usr/local/var/openldap/replog.slave.YourCompany.com:389 and exit, use the following command: slurpd -r /usr/tmp/replog.slave.YourCompany.com:389 -o

Referrals are one way to extend the scope of your directory beyond a single server and, if you so desire, add it to a global network linked much like DNS. The concept of referrals is inherited from X.500. You can approach the concept of referrals in two ways, described next.

The first is to look at them like root server lists in DNS, in that each server has a superior server that ultimately is authoritative for providing lists (or referrals) to other servers in order to create a global directory hierarchy. This is implemented in DNS resource records for service locations, as defined by RFC 2782. Most existing LDAP implementations don t support the location of directory services using DNS SRV resource records. However, most services support generation of referrals to superior servers. Using these records in DNS is akin to mail servers discovering and utilizing mail exchange (MX) hosts or a client looking at a global directory to request information. If an LDAP client adhering to RFC 2782 standards wants to discover an LDAP server that supports TCP and provides LDAP services for YourCompany.com, it would look up the following: _ldap._tcp.YourCompany.com The format for the SRV RR is as follows: _Service._Proto.Name TTL Class SRV Priority Weight Port Target The options are as follows: Service: This is the symbolic name for the desired service with an underscore prepended so that it isn t confused with typical DNS information. Proto: This is the symbolic name of the desired protocol. Currently, _TCP and _UDP would be the best candidates for inclusion here. Name: This is the domain to which this resource record refers. TTL: This is the RFC 1035-compliant time to live, or the expiration. Class: This is the RFC 1035-compliant class. SRV records occur in the IN Class. Priority: This is the priority of this target host. A client must attempt to contact the target host with the lowest-numbered priority it can reach. Target hosts with the same priority should be tried in an order defined by the weight field.

Weight: This is a server selection mechanism. The weight field specifies a relative weight for entries with the same priority. Large weights should be given a proportionately higher probability of being selected. Port: This is the port on this target host that s used for this service. LDAP will use port 389 for standard communications and 636 for secure communications. Target: This is the domain name of the target host. There must be one or more address records for this name, and it must not be an alias. A target of . indicates that the service isn t available at this particular domain. The overall goal of using these resource records in your DNS tables is to provide clients with a way to retrieve well-known services (WKS) without the need of being preconfigured. The original problem statement may have been an Internet service provider requiring a list of configuration options including MAIL, POP3, IMAP4, NNTP and other services. Resource , records publishing names of these services in a standard way would solve many of the issues surrounding the maintenance of lists. Global referrals are a complement to this type of configuration. The root service locates services associated with a given fully qualified domain name by querying DNS for the LDAP SRV resource records. For the domain YourCompany.Com, the service would issue an SRV query for _ldap._tcp.YourCompany.Com, as explained previously. A successful query will return one or more resource records of the following form: ldap.tcp.YourCompany.Com. IN SRV 0 0 389 ldap.YourCompany.Com. For each record that is returned, an LDAP URL is constructed. From this example record, the URL would be as follows: ldap://ldap.YourCompany.Com:389/ These URLs are then returned in the referral. The referral is then used to forward information to various servers configured among the network of LDAP servers to which your host belongs.