mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #24] "Invalid username or password" #16
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#16
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 @Kuuchuu on GitHub (Jul 4, 2021).
Original GitHub issue: https://github.com/lldap/lldap/issues/24
No matter what I try I'm unable to log in. Currently using the docker image, but I had the same issue when I set it up without docker before there was an image for it. It's running behind a reverse proxy, swag to be specific. Web page loads up no issue. I put in the username/password I set up but it says invalid. I've tried all sorts of combinations of things. I set the password/username in the toml file and in env variables, and tried not changing the username from "admin". No luck. Tried setting the password to something simple just in case it didn't like one of my characters, no change. I tried both binding the data directory to a folder and letting docker create a volume for it. Any help and/or guidance would be greatly appreciated, thanks!
@nitnelave commented on GitHub (Jul 5, 2021):
Hey! Thanks for using LLDAP :) Just a quick disclaimer, it's not ready to use yet, it's missing core functionality. But it should work enough to log in as admin, though.
Just to be sure, with the default config, and the given values:
you can't login with the login/pass "admin"/"12345"?
If so, please try this:
@nitnelave commented on GitHub (Jul 5, 2021):
After some investigation, I found a recently introduced error in the initial setup: we never set the admin password! That explains the issue. Fixed by #26.