mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #813] [FEATURE REQUEST] Add support for https #292
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#292
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ykhemani on GitHub (Jan 23, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/813
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.
@nitnelave commented on GitHub (Jan 23, 2024):
Reverse proxy is the recommended setup. Is there any reason that doesn't work for you?
@ykhemani commented on GitHub (Jan 24, 2024):
Indeed, it can work. Having this allows you to have end-to-end encryption without another layer.
@nitnelave commented on GitHub (Jan 24, 2024):
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.
@fsdrw08 commented on GitHub (Apr 10, 2024):
Any updates for this request?
@nitnelave commented on GitHub (Apr 10, 2024):
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.