Skip found LDAP objects that miss required attributes #49
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
…butes but don't contain the required attribute. Original fix by Fred, cherry-picked by Maurits.
|
Thank you! |
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.
Skip objects that were found in LDAP while searching on several attributes but don't contain the required attribute. We see this on the sharing tab when searching for ('van').
(Somehow when this error occurs, the LDAP (or maybe memcache) does not find any users in future requests, until you restart the Zope instance, but that is a separate issue.)
Original fix by Fred, cherry-picked by Maurits.
This replaces PR #37. Not sure if there is anything left to do for that one.
cc @rnixx