Allow raw `tls_options` to be passed in LDAP configuration
What does this MR do?
It's the GitLab counterpart to omniauth-ldap!12 (merged). It exposes the full tls_options hash so users can set any LDAP TLS options, like ssl_version, ca_file or ciphers. Basically, anything OpenSSL supports...
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
We're seeing more and more customers in highly secure environments and they need the ability to set specific ciphers that are allowed. In many cases, without the ability to restrict ciphers, LDAP was simply not allowing connections.
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 - Conforms to the code review guidelines
-
Has been reviewed by a UX Designer -
Has been reviewed by a Frontend maintainer -
Has been reviewed by a Backend maintainer -
Has been reviewed by a Database specialist
-
-
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
If you have multiple commits, please combine them into a few logically organized commits by squashing them -
Internationalization required/considered -
End-to-end tests pass ( package-and-qamanual pipeline job)
What are the relevant issue numbers?
Edited by Drew Blessing