Removed jpegphoto attribute when photo sync isn't enabled#168
Merged
Conversation
Shadowghost
approved these changes
Oct 29, 2024
crobibero
approved these changes
Oct 29, 2024
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Currently the
LocateLdapUsermethod will always try and find users with thejpegphotoattribute. This is not always guaranteed to be permitted however especially with some more privacy centric LDAP servers such as kanidm. As such thejpegphotoattribute should only be included in the search if profile photo sync is enabled.While I was at it I took the liberty to bump the StyleCop analyzer version to make it compatible with the new collection initialization syntax.