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
4ef042fe
Commit
4ef042fe
authored
22 years ago
by
Kurt Zeilenga
Browse files
Options
Downloads
Patches
Plain Diff
Clean up filters
parent
44c214d4
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/guide/admin/sasl.sdf
+6
-5
6 additions, 5 deletions
doc/guide/admin/sasl.sdf
with
6 additions
and
5 deletions
doc/guide/admin/sasl.sdf
+
6
−
5
View file @
4ef042fe
...
...
@@ -483,10 +483,10 @@ statements of the form:
> uid=(.*),cn=digest-md5,cn=auth
> ldap:///dc=customers,dc=example,dc=com??sub?(&(uid=$1)(objectClass=person))
Note that the explicitly-named realms are handled first, to avoid
the
realm name becoming part of the UID. Note also the limitation
of
matches to those entries with objectClass=person to
avoid matching
other entries that happen to refer to the UID.
Note that the explicitly-named realms are handled first, to avoid
the
realm name becoming part of the UID. Note also the limitation
of
matches to those entries with
{{EX:(
objectClass=person
)}}
to
avoid matching
other entries that happen to refer to the UID.
See {{slapd.conf}}(5) for more detailed information.
...
...
@@ -657,7 +657,7 @@ source rule like
would allow that authenticated user to authorize to any DN that
matches the regular expression pattern given. This regular expression
comparison can be evaluated much faster than an LDAP search for
"
uid=*
"
.
{{EX:(
uid=*
)}}
.
Also note that the values in an authorization rule must be one of
the two forms: an LDAP URL or a DN (with or without regular expression
...
...
@@ -665,6 +665,7 @@ characters). Anything that does not begin with "ldap://" is taken
as a DN. It is not permissable to enter another authorization
identity of the form "u:<username>" as an authorization rule.
H4: Policy Configuration
The decision of which type of rules to use, {{EX:saslAuthzFrom}}
...
...
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