mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #471] lldap hates me (or hates my name) #176
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#176
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 @RoryNesbitt on GitHub (Mar 11, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/471
So I don't really know how to debug this but I promise it's not a joke.
My name is Rory, quite a good name if I do say so myself. However lldap doesn't seem to think so. If I create a user with the uid rory I can't use it through authelia.
I'm running both lldap and authelia on unraid. My authelia config looks very much like the example in this repo, and I can log in to any of the lldap users I make, except if I call them rory. rory can however log in directly to lldap.
There is nothing in the logs, except a lack of logs. if I use a different user and a bad password I get an ERROR. But, If I use the rory user this error never appears, whether I use the correct password or the wrong one.
@martadinata666 commented on GitHub (Mar 11, 2023):
jokes aside, is another 4 chars name work fine? 🤔 roru tori tory, etc. As base config uid admin seems work for 5chars.
@RoryNesbitt commented on GitHub (Mar 11, 2023):
I swear to you I tested the name 'test' exactly for this reason. but now when I go to confirm it I get the same issueOkay I had some issue with traefik, looked like it made the user but it didn't. Tested directly via the ip address
User 'roru' works and logs in fine
@martadinata666 commented on GitHub (Mar 11, 2023):
how about the password? is it also 4 char? I think lldap looking for 8 char.
@RoryNesbitt commented on GitHub (Mar 11, 2023):
Password is consistently 8 or more characters. lldap doesn't let you create the user with a shorter one
@RoryNesbitt commented on GitHub (Mar 11, 2023):
this is honestly insane.
So just there after thinking it was the length I made a user 'tes', which worked fine. so I made the user 'roru', again fine.
So then I delete those and make 'rory' again with the same email as roru and the same password as roru and nothing else filled in. Doesn't work
@martadinata666 commented on GitHub (Mar 11, 2023):
set verbose true in config, and attach lldap log here. let's see what magical rory doing, pretty interesting. FYI I'm trying to replicate it but I can't, and I'm on stable 0.4.1. Dunno if that will make diff.
@RoryNesbitt commented on GitHub (Mar 11, 2023):
lldap.log
So as I say, nothing pops up when I try to log in from authelia, but for this one what I done was
@RoryNesbitt commented on GitHub (Mar 11, 2023):
So uhm, authelia had blocked the rory user, and even when the user was deleted and recreated the block would persist. turns out this has nothing to do with lldap.
oops