SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG
DONATE


YUM REPOSITORY

 
 

MAN page from PLD openldap-2.0.27-1.i386.rpm

UD.CONF

Section: File Formats (5)
Updated: 20 August 2000
Index 

NAME

ud.conf - ud configuration file 

SYNOPSIS

/etc/openldap/ud.conf 

DESCRIPTION

Theudconfiguration file is used to set system-wide defaults to be applied whenrunningud.Note that each user may specify an optional configuration file,.udrc,in his/her home directory which will be used instead of the system-wideconfiguration file. 

OPTIONS

The different configuration options are:
HOST <name>
Used to specify the name of an LDAP server to which ud should connect. There may be only one entry per config file.The server's name can be specified as a domain-style name or an IP address.
BASE <base>
Used to specify the search base to use when performing search operations.The base may be changed by those usingudby using thecbcommand.There may be only one entry per config file.The base must be specified as a Distinguished Name in LDAP format.
GROUPBASE <base>
Used to specify the base used when creating groups.The base may be changed by those usingudby using the changegroupcommand.There may be only one entry per config file.The base must be specified as a Distinguished Name in LDAP format.
SEARCH <algorithm>
Used to specify a search algorithm to use when performing searches. More thanone algorithm may be specified, and each is tried in turn until a suitableresponse is found.

Each algorithm specifies a filter that should be used when performing a findoperation. Filters contain LDAP-style attribute types (e.g., uid, cn,postalAddress)and operators to test for equality or approximate equality. Prefix operatorsmay also be used to specify AND, OR and NOT operations (see ldap(3) formore details on the filter format). Algorithms use acompile-time constant as a separator to use when parsing the input the userhas provided. This parsed input can then be referenced similarly to anawkprogram using symbols like $1, $2, and $0 for the entire batch of input.

For example, the algoritmcn=$0causesudto perform a lookup on the entire string the user has typed, searching for anything where the commonName exactly matches the whole thing.

Another example,sn~=$NFcausesudto do a search where the last element the user has typed (NF = number of fieldsand is a special "number" that can be used inawkas well asud)searching for any matches that approximately match Surname.

Search algorithms also support a special feature which allows one to specifythe exactnumber of fields that must be present in order for the algorithm to beapplied. This number must be specified between square brackets.

For example,[1] uid=$1causes this algorithm to be applied when the number of fields is exactly equalto one. If there is exactly one field, the token is looked up as a UID.

 

FILES

/etc/openldap/ud.conf 

SEE ALSO

ud(1),ldap(3) 

AUTHOR

Bryan Beecher, University of Michigan 

ACKNOWLEDGEMENTS

is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).is derived from University of Michigan LDAP 3.3 Release.


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
FILES
SEE ALSO
AUTHOR
ACKNOWLEDGEMENTS

This document was created byman2html,using the manual pages.