mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #229] Unable to login #79
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#79
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 @Abraka on GitHub (Jul 8, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/229
Iv got lldap_config.toml with user and password parameters...password has 8 charakcters. Still unbale to login. Docker installation.
@nitnelave commented on GitHub (Jul 8, 2022):
Can you restart the server in verbose mode and paste the logs? How are you trying to log in? Via the web interface or through LDAP ?
@Abraka commented on GitHub (Jul 8, 2022):
docker run -d --name=lldap -e PUID=1100 -e PGID=1100 -p 3890:3890 -p 17170:17170 -v /home/lldap/lldap_data:/data --restart unless-stopped nitnelave/lldap:stableLogin via web interface
Verbose:
@martadinata666 commented on GitHub (Jul 9, 2022):
If you use
lldap_config.tomlkindly attach it. im thinking you are missing JWT part. As your startup command missing some bits that neededdocker run -d --name=lldap -e PUID=1100 -e PGID=1100 -p 3890:3890 -p 17170:17170 -v /home/lldap/lldap_data:/data --restart unless-stopped nitnelave/lldap:stablealso there is no PUID PGID.@Abraka commented on GitHub (Jul 9, 2022):
lldap_config.txt
@martadinata666 commented on GitHub (Jul 9, 2022):
Tried your
lldap_config.tomlfrom cleandatadirectory it works.my compose
@nitnelave commented on GitHub (Jul 9, 2022):
Did you change the admin's password in the UI? It might not match the config anymore.
@nitnelave commented on GitHub (Jul 9, 2022):
The verbose logs you provided don't show the login attempt. Could you start the server, attempt to login once, and then copy the logs? ideally starting from
Starting "lldap" service.And don't forget to put the logs in a code block when you paste it, surrounded by ```
@Abraka commented on GitHub (Jul 9, 2022):
No, I open page for login and type admin and Ldap222 ...which give me a "Invalid username or password"
@Abraka commented on GitHub (Jul 9, 2022):
@martadinata666 commented on GitHub (Jul 9, 2022):
Looking from the logs im assuming that
lldap_config.tomlnot exist at first?@Abraka commented on GitHub (Jul 9, 2022):
@martadinata666 commented on GitHub (Jul 9, 2022):
So that is our problem,
Tldr: the modified config must exist first
@Abraka commented on GitHub (Jul 9, 2022):
I kept modified conf and give 777 on all. Deployed new container and now its running and I can login...finally!
Its still creating new files inside data folde with 1000:1000 gid which you put as hardcoded in image.
@martadinata666 commented on GitHub (Jul 9, 2022):
Yep, right now still hardcoded to user 1000, maybe need some gosu or su-exec to add some
UIDsupports in future.@nitnelave commented on GitHub (Jul 9, 2022):
@martadinata666 can you open an issue to track support for UID/GID?