mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 16:25:55 +03:00
[GH-ISSUE #1095] Unable to login to web ui as admin #396
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#396
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 @crypticscribe on GitHub (Feb 3, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1095
Describe the bug
I'm unable to login to the web UI as the admin user after spinning up the docker container, creating the volume, and customizing the config files.
My docker-compose.yml
My lldap_config.toml
Expected behavior
Able to login as admin
Logs
Web Logs
Server Logs
Additional context
I've tried setting the password, not setting the password, forcing the password reset, and deleting the user db.
@nitnelave commented on GitHub (Feb 3, 2025):
What was the issue? I try to make the error messages as explicit as possible, it's always good to hear about new failure cases (even PEBCAK)
@crypticscribe commented on GitHub (Feb 4, 2025):
The error messages and logs were great. I only saw the issue because the logs were so verbose. The issue was the ldap_base_dn wasn't correct in lldap_config on my volume. Since it was a misconfiguration everything was functioning as it should, so login failed, but no errors were thrown. I only saw it after posting this and seeing all the logs and config files at once. I assume base_dn was the last thing I changed in ldap_config and I forgot to save it before copying it, since everything else copied over to the volume fine. After changing that to the correct base_dn everything is working now.