LDAP: numeric uid/gid fallback to nobody(99) #1848
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
butonic
force-pushed
the
ldap-nobody-fallback
branch
from
48193b3
to
524e6c5
Compare
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
butonic
force-pushed
the
ldap-nobody-fallback
branch
from
524e6c5
to
69a1acc
Compare
ishank011
approved these changes
Jul 1, 2021
labkode
pushed a commit
to glpatcern/reva
that referenced
this pull request
Jul 1, 2021
thmour
pushed a commit
to thmour/reva
that referenced
this pull request
Jul 12, 2021
21 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When an LDAP server does not provide numeric uid or gid properties for a user we now fall back to a configurable
nobodyid (default 99).