Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
OpenLDAP
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue 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
Jaak Ristioja
OpenLDAP
Commits
947f4183
Commit
947f4183
authored
21 years ago
by
Pierangelo Masarati
Browse files
Options
Downloads
Patches
Plain Diff
more clarifications on dnstyle usage
parent
c8f62b12
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
+35
-2
35 additions, 2 deletions
doc/man/man5/slapd.access.5
with
35 additions
and
2 deletions
doc/man/man5/slapd.access.5
+
35
−
2
View file @
947f4183
...
...
@@ -591,8 +591,7 @@ access to the attribute holding the referral information
attribute).
.SH CAVEATS
It is strongly recommended to explicitly use the most appropriate
DN
.BR style ,
.BR <dnstyle> ,
to avoid possible incorrect specifications of the access rules as well
as for performance (avoid unrequired regex matching when an exact
match suffices) reasons.
...
...
@@ -624,6 +623,40 @@ For performance reasons, it would be better to use the subtree style.
by ...
.fi
.LP
When writing submatch rules, it may be convenient to avoid unnecessary
.B regex
.B <dnstyle>
use; for instance, to allow access to the subtree of the user
that matches the
.B what
clause, one could use
.LP
.nf
access to dn.regex="^(.+,)?uid=([^,]+),dc=example,dc=com$$"
by dn.regex="^uid=$1,dc=example,dc=com$$" write
by ...
.fi
.LP
However, since all that is required in the
.B to
clause is substring expansion, a more efficient solution is
.LP
.nf
access to dn.regex="^(.+,)?uid=([^,]+),dc=example,dc=com$$"
by dn.exact,expand="uid=$1,dc=example,dc=com" write
by ...
.fi
.LP
In fact, while a
.B <dnstyle>
of
.B regex
implies substring expansion,
.BR exact ,
as well as all the other DN specific
.B <dnstyle>
values, does not, so it must be explicitly requested.
.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