Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
OpenLDAP
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Christopher Ng
OpenLDAP
Commits
904f5130
Commit
904f5130
authored
21 years ago
by
Pierangelo Masarati
Browse files
Options
Downloads
Patches
Plain Diff
clarify DN regex match quirks
parent
0f2bb9f0
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/man/man5/slapd.access.5
+42
-0
42 additions, 0 deletions
doc/man/man5/slapd.access.5
with
42 additions
and
0 deletions
doc/man/man5/slapd.access.5
+
42
−
0
View file @
904f5130
...
...
@@ -425,6 +425,48 @@ or the (even more silly) example
.LP
which grants everybody search and compare privileges, and adds read
privileges to authenticated clients.
.SH CAVEATS
It is strongly recommended to explicitly use the most appropriate
DN
.BR style ,
for performance (avoid unrequired regex matching when
an exact match suffices) but also to avoid possible
misimplementations of the access rules.
In fact, a rule of the form
.LP
.nf
access to dn="dc=example,dc=com"
by ...
.fi
.LP
implies that all the subtree "dc=example,dc=com" matches, and the
match is done using a regex.
.LP
.nf
access to dn.subtree="dc=example,dc=com"
by ...
.fi
.LP
would be far more appropriate.
.LP
Another quirk is related to the
.B by
clause:
a rule of the form
.LP
.nf
access to *
by dn="cn=User,dc=example,dc=com" write
.fi
.LP
gives write access to every DN below "cn=User,dc=example,dc=com";
if only that DN should have write access, the correct rule would be
.LP
.nf
access to *
by dn.exact="cn=User,dc=example,dc=com" write
.fi
.LP
.SH FILES
.TP
ETCDIR/slapd.conf
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment