We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
in light of the issue patched by the v2.3.2 and the fact glauth/ldap is actively miantained by glauth it might be a good time to drop the current monitoring implementation and shift it directly to https://github.com/glauth/ldap/blob/master/server.go#L68 as it was sugegsted in #351 (comment)
glauth/ldap
The text was updated successfully, but these errors were encountered:
Makes perfect sense. Can we however make sure to use dependency injection, so we can easily track any upstream ldap updates over time?
Sorry, something went wrong.
No branches or pull requests
in light of the issue patched by the v2.3.2 and the fact
glauth/ldap
is actively miantained by glauth it might be a good time to drop the current monitoring implementation and shift it directly to https://github.com/glauth/ldap/blob/master/server.go#L68 as it was sugegsted in #351 (comment)The text was updated successfully, but these errors were encountered: