mirror of
https://git.openldap.org/openldap/openldap.git
synced 2025-12-24 00:29:35 -05:00
provide a useful example
This commit is contained in:
parent
ee2c377d08
commit
9ba68f902d
1 changed files with 19 additions and 0 deletions
|
|
@ -806,6 +806,25 @@ or the (even more silly) example
|
|||
.LP
|
||||
which grants everybody search and compare privileges, and adds read
|
||||
privileges to authenticated clients.
|
||||
.LP
|
||||
One useful application is to easily grant write privileges to an
|
||||
.B updatedn
|
||||
that is different from the
|
||||
.BR rootdn .
|
||||
In this case, since the
|
||||
.B updatedn
|
||||
needs write access to (almost) all data, one can use
|
||||
.LP
|
||||
.nf
|
||||
access to *
|
||||
by dn.exact="cn=The Update DN,dc=example,dc=com" write
|
||||
by * break
|
||||
.fi
|
||||
.LP
|
||||
as the first access rule.
|
||||
As a consequence, unless the operation is performed with the
|
||||
.B updatedn
|
||||
identity, control is passed straight to the subsequent rules.
|
||||
.SH OPERATION REQUIREMENTS
|
||||
Operations require different privileges on different portions of entries.
|
||||
The following summary applies to primary database backends such as
|
||||
|
|
|
|||
Loading…
Reference in a new issue