Repository navigation
fix(users): improve LDAP error handling - #618
Merged
Merged
Conversation
Set a proper "unavailable" status that the caller can handle when the LDAP lookup failed because the LDAP server is unavailable instead of always returning "not found".
Member
Author
|
@aduffeck I basically need this for the space-member migration, but IMO this is generic enough to go into the main branch directly. |
aduffeck
approved these changes
May 6, 2026
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
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.
Set a proper "unavailable" status that the caller can handle when the LDAP lookup failed because the LDAP server is unavailable instead of always returning "not found".