upstream/openldap
1
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2025-12-23 16:19:35 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

clarify the usage of the <modifier> field in 'dn' and 'domain' clauses of <who> access directive

Browse source
This commit is contained in:
Pierangelo Masarati 2003-11-01 14:14:09 +00:00
parent e0999334d2
commit 9620cacd34
1 changed files with 26 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
doc/man/man5/slapd.access.5
View file

@ -216,6 +216,16 @@ dn.regex clause by using the form
with
.B digit
ranging from 1 to 9.
The style qualifier
allows an optional
.BR modifier .
At present, the only type allowed is
.BR expand ,
which causes substring substitution of submatches to take place
even if
.B dnstyle
is not
.BR regex .
.LP
The statement
.B dnattr=<attrname>
@ -299,6 +309,22 @@ of the contacting host is determined by performing a DNS reverse lookup.
As this lookup can easily be spoofed, use of the
.B domain
statement is strongly discouraged. By default, reverse lookups are disabled.
The optional
.B domainstyle
qualifier of the
.B domain
clause allows a
.B modifier
option; the only value currently supported is
.BR expand ,
which causes substring substitution of submatches to take place even if
the
.B domainstyle
is not
.BR regex ,
much like the analogous usage in
.B dn
clause.
.LP
The statement
.B set=<pattern>