mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #1122] I'm too stupid for LDAPS #398
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#398
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 @darkwolf1000 on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1122
Describe the bug
Tried uncomment LDAPS things but just got an error
To Reproduce
Steps to reproduce the behavior:
I tried uncommenting
got error
0: while setting up the SSL certificate
1: No such file or directory (os error 2)
Got
-rw-r--r-- 1 1000 1000 2216 Mar 4 18:50 ldap.crt
-rw------- 1 1000 1000 3272 Mar 4 18:49 ldap.key
in my cert folder
tried my own certificates with same RW rules got the same error
Expected behavior
To be honest not sure it never worked for me
Logs
Loading configuration from /data/lldap_config.toml
WARNING: A key_seed was given, we will ignore the key_file and generate one from the seed! Set key_file to an empty string in the config to silence this message.
WARNING: Unsecure default admin password is used.
2025-03-04T18:03:42.196783102+00:00 INFO set_up_server [ 40.3ms | 100.00% ]
2025-03-04T18:03:42.196803600+00:00 INFO ┝━ ｉ [info]: Starting LLDAP version 0.6.1
2025-03-04T18:03:42.244786321+00:00 INFO ┕━ ｉ [info]: Starting the LDAP server on port 3890
Error: while binding the LDAP server
Caused by:
Additional context
Host Arch VM using Portainer
Sorry if this is a duplicate but it's not described well enough to enable LDAPS
@nitnelave commented on GitHub (Mar 4, 2025):
Make sure that the files exist at the correct path inside the container, and that the container user has the right to read them. That's very setup-dependent, so there's not much more I can help with :/
@darkwolf1000 commented on GitHub (Mar 4, 2025):
The files created them self at the first try and are in the right directory but for some reason there is now a cert folder in my cert folder with
drwxr-xr-x 2 1000 1000 4 Mar 4 18:55 certs
and the files
-rw-r--r-- 1 1000 1000 2212 Mar 4 18:55 ldap.crt
-rw------- 1 1000 1000 3272 Mar 4 18:55 ldap.key
UID:1000
GID:1000
@nitnelave commented on GitHub (Mar 4, 2025):
With the config that you posted, there should be in the container a ldap.crt file in the root folder (/ldap.crt)
Is that the case (again, inside the container)? How do you mount the files?
@darkwolf1000 commented on GitHub (Mar 4, 2025):
lldap:
image: lldap/lldap:stable
ports:
- "389:3890"
- "636:6360"
- "17170:17170"
volumes:
- "/etc/lldap/lldap_data:/data"
# Alternatively, you can mount a local folder
# - "./lldap_data:/data"
environment:
- UID=1000
- GID=1000
- TZ=Europe/Berlin
- LLDAP_JWT_SECRET=yes
- LLDAP_KEY_SEED=yes
- LLDAP_LDAP_BASE_DN="yes"
- LDAP_USER_DN = "yes"
- LDAP_USER_PASS = "yes"
# If using LDAPS, set enabled true and configure cert and key path
- LLDAP_LDAPS_OPTIONS__ENABLED=true
- LLDAP_LDAPS_OPTIONS__CERT_FILE=/ldap.crt
- LLDAP_LDAPS_OPTIONS__KEY_FILE=/ldap.key
Files are like
all from lldap is owed by 1000 with RW rules set by the container
@nitnelave commented on GitHub (Mar 4, 2025):
Apologies if I'm misreading, but you don't seem to actually mount the ldap.crt file, at least in the docker config you shared. Is it inside /data?
@darkwolf1000 commented on GitHub (Mar 4, 2025):
Its not
i forgot that
(and i tried /etc/lldap/certs:/certs with ...KEY_FILE=/certs/ldap.key)
was
at first
@nitnelave commented on GitHub (Mar 4, 2025):
Right, but AFAICT those files are not mounted inside the container. They exist outside, but not inside. Does what I say make sense?
@darkwolf1000 commented on GitHub (Mar 4, 2025):
even when copied to the lldap_data folder i get the same error with
even when they are mounted to /data/ldap.crt the won't get loaded
@darkwolf1000 commented on GitHub (Mar 4, 2025):
nvm i forgor /data in front of the ldap.crt
cert files are now just thrown in /lldap_data