-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
[FEATURE REQUEST] Add support for https #813
Comments
Reverse proxy is the recommended setup. Is there any reason that doesn't work for you? |
Indeed, it can work. Having this allows you to have end-to-end encryption without another layer. |
Alright, since we have a working solution, I'm not going to fix it myself. If someone wants to come and implement it, be my guest. |
Any updates for this request? |
See the message above: I'm not going to work on that, but I'll accept contributions. Note that a reverse proxy that provides HTTPS to the external world but HTTP inside the host is often more than enough. |
Motivation
Allow secure (https) communication for the web interface to lldap so that communication between the browser and lldap isn't in plaintext.
Describe the solution you'd like
Describe alternatives you've considered
You could use a reverse proxy and have it terminate TLS. The connection from the reverse proxy to lldap would still be clear text, of course.
The text was updated successfully, but these errors were encountered: