New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance LDAP errors handling #14561
Enhance LDAP errors handling #14561
Conversation
As draft for now, for first feedbacks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
This is really a great move here. We should always use defensive code when dealing with a remote service, especially when it involves dynamic data entered by the end user.
I think it could be a good idea to add tests that validates that all these failing cases are producing helpful messages, at least with openldap
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK for me now.
We could probably add tests, and maybe improve some messages (tests would help to see what we will push in logs).
179d37a
to
fea87c1
Compare
fea87c1
to
4010301
Compare
Silent error in status checker Properly handle non existing group Deprecate dead 'clean' parameter Handle LDAP_NO_SUCH_OBJECT error response from LDAP Fix return types; limit encapsulation, simplify code Deprecated useless param Handle errors on `ldap_parse_result`
4010301
to
0a5a624
Compare
Meant to replace #14356