mirror of
https://git.openldap.org/openldap/openldap.git
synced 2024-12-21 03:10:25 +08:00
Reminder to RTFM. Fix typo.
This commit is contained in:
parent
e16ad51b5a
commit
cfbe95dbae
@ -25,8 +25,9 @@ rights (i.e. auth, search, compare, read and write) on everything and anything.
|
||||
As a consequence, it's useless (and results in a performance penalty) to explicitly
|
||||
list the {{rootdn}} among the {{<by>}} clauses.
|
||||
|
||||
The following sections will describe Access Control Lists in more details and
|
||||
follow with some examples and recommendations.
|
||||
The following sections will describe Access Control Lists in greater depth and
|
||||
follow with some examples and recommendations. See {{slapd.access}}(5) for
|
||||
complete details.
|
||||
|
||||
H2: Access Control via Static Configuration
|
||||
|
||||
@ -1322,7 +1323,7 @@ The end result is that when Jane accesses John's entry, she will be granted
|
||||
write access to the specified attributes. Better yet, this will happen to any
|
||||
entry she accesses which has Mary as the manager.
|
||||
|
||||
This is all cool and nice, but perhaps gives to much power to secretaries. Maybe we need to further
|
||||
This is all cool and nice, but perhaps gives too much power to secretaries. Maybe we need to further
|
||||
restrict it. For example, let's only allow executive secretaries to have this power:
|
||||
|
||||
> access to dn.exact="uid=john,ou=people,dc=example,dc=com"
|
||||
|
Loading…
Reference in New Issue
Block a user