Penguin
Recent Changes
Annotated edit history of ud.conf(5) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 UD.CONF
2 !!!UD.CONF
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 OPTIONS
7 FILES
8 SEE ALSO
9 AUTHOR
10 ACKNOWLEDGEMENTS
11 ----
12 !!NAME
13
14
15 ud.conf - ud configuration file
16 !!SYNOPSIS
17
18
19 /etc/ldap/ud.conf
20 !!DESCRIPTION
21
22
23 The ''ud'' configuration file is used to set system-wide
24 defaults to be applied when running ''ud''. Note that
25 each user may specify an optional configuration file,
26 ''.udrc'', in his/her home directory which will be used
27 instead of the system-wide configuration file.
28 !!OPTIONS
29
30
31 The different configuration options are:
32
33
34 __HOST __
35
36
37 Used to specify the name of an LDAP server to which
38 ''ud'' should connect. There may be only one entry per
39 config file. The server's name can be specified as a
40 domain-style name or an IP address.
41
42
43 __BASE __
44
45
46 Used to specify the search base to use when performing
47 search operations. The base may be changed by those using
48 ''ud'' by using the ''cb'' command. There may be only
49 one entry per config file. The base must be specified as a
50 Distinguished Name in LDAP format.
51
52
53 __GROUPBASE __
54
55
56 Used to specify the base used when creating groups. The base
57 may be changed by those using ''ud'' by using the
58 ''changegroup'' command. There may be only one entry per
59 config file. The base must be specified as a Distinguished
60 Name in LDAP format.
61
62
63 __SEARCH __
64
65
66 Used to specify a search algorithm to use when performing
67 searches. More than one algorithm may be specified, and each
68 is tried in turn until a suitable response is
69 found.
70
71
72 Each algorithm specifies a filter that should be used when
73 performing a find operation. Filters contain LDAP-style
74 attribute types (e.g., uid, cn, postalAddress) and operators
75 to test for equality or approximate equality. Prefix
76 operators may also be used to specify AND, OR and NOT
77 operations (see ldap(3) for more details on the filter
78 format). Algorithms use a compile-time constant as a
79 separator to use when parsing the input the user has
80 provided. This parsed input can then be referenced similarly
81 to an ''awk'' program using symbols like $1, $2, and $0
82 for the entire batch of input.
83
84
85 For example, the algoritm ''cn=$0'' causes ''ud'' to
86 perform a lookup on the entire string the user has typed,
87 searching for anything where the commonName exactly matches
88 the whole thing.
89
90
91 Another example, ''sn~=$NF'' causes ''ud'' to do a
92 search where the last element the user has typed (NF =
93 number of fields and is a special
94 ''awk'' as well as ''ud'') searching
95 for any matches that approximately match
96 Surname.
97
98
99 Search algorithms also support a special feature which
100 allows one to specify the ''exact'' number of fields that
101 must be present in order for the algorithm to be applied.
102 This number must be specified between square
103 brackets.
104
105
106 For example, ''[[1] uid=$1'' causes this algorithm to be
107 applied when the number of fields is exactly equal to one.
108 If there is exactly one field, the token is looked up as a
109 UID.
110 !!FILES
111
112
113 ''/etc/ldap/ud.conf''
114 !!SEE ALSO
115
116
117 ud(1), ldap(3)
118 !!AUTHOR
119
120
121 Bryan Beecher, University of Michigan
122 !!ACKNOWLEDGEMENTS
123
124
125 __OpenLDAP__ is developed and maintained by The OpenLDAP
126 Project (http://www.openldap.org/). __OpenLDAP__ is
127 derived from University of Michigan LDAP 3.3
128 Release.
129 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.