LDAP: only use proxy classes as backend #4556
Merged
Conversation
This file contains hidden or 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
|
@blizzz, thanks for your PR! By analyzing the history of the files in this pull request, we identified @nickvergessen, @GitHubUser4234 and @MorrisJobke to be potential reviewers. |
Signed-off-by: Arthur Schiwon <[email protected]>
blizzz
force-pushed
the
downstream-ldap-78
branch
from
7e98866 to
a9a80f9
Compare
LukasReschke
approved these changes
May 8, 2017
rullzer
approved these changes
May 8, 2017
This was referenced Sep 16, 2021
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.
Downstream of owncloud/user_ldap#78
The only benefit is easier maintenance of the app launch code.
The downside is a small layer between the actual user backend and the user manager (and groups). This is the case anyway when more than one server is registered. Rather negligible.
@nextcloud/ldap