You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current AD functionality is limited as it only works with the ldap:// protocol. The underlying libraries, however, do support secure connections.
Hajk's backend should be extended to make it possible to provide necessary TLS certificate files, read them, and establish a secure connection to LDAP via TLS.
The text was updated successfully, but these errors were encountered:
- No changes for current setups: if you're happy without TLS, you don't need to do anything.
- If you want to connect to an LDAPS service, you can now do that by providing the necessary certificates and/or passphrase.
- I've also added some checks that should've been there before: we check the connection to LDAP(S) service at startup and abort if it fails. Previously (without the check at startup) we'd run into problems when the first user's request came in. That's a bit late, as it's easier to detect and fix errors if the Backend service fails already at startup.
I think it depends on which version of NodeJS you're running, @larsam0524 . Please see the official documentation. Perhaps there is some more specific information there.
The current AD functionality is limited as it only works with the ldap:// protocol. The underlying libraries, however, do support secure connections.
Hajk's backend should be extended to make it possible to provide necessary TLS certificate files, read them, and establish a secure connection to LDAP via TLS.
The text was updated successfully, but these errors were encountered: