Default LDAP config verify_certificates to true
What does this MR do?
Defaults LDAP config verify_certificates to true.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
This is known to be a breaking change for some subset of installations, which is why we defaulted to false when we added the option. We released it with warnings in blog posts, in the configuration, and in the docs, saying that we will change the default to true in a later release. It is now time to make the default secure, since the users of installations configured with SSL or TLS LDAP configs believe their LDAP connections are secure.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together
What are the relevant issue numbers?
Edited by Michael Kozono