-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Fix login as non ldap user #568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@icewind1991, thanks for your PR! By analyzing the annotation information on this pull request, we identified @blizzz, @MorrisJobke and @dschmidt to be potential reviewers |
|
The login works for me even without this change. Could you please comment what this change will address? |
|
I'm not sure about the exact reason but when trying to make a dav request for a non ldap user (while having ldap users configured) |
|
@blizzz Any comment on this? |
|
I am bewildered, need to verify. |
|
@icewind1991 I cannot verify the issue do you have detailed reproduction steps? |
|
No, it probably depends on the specific ldap setup but I don't have enough ldap knowledge to know why |
|
What might happened here is that the provided loginname resulted into an LDAP result when looking up a user for the provided loginname. Then there are only few cases were it could fail, e.g. there is no displayname set on LDAP for that user (should result in a log line like But because we do not check for null in that case it does not gracefully deny login for that LDAP user, but ends up with an error. The check could be reverted to only look for |
|
@icewind1991 Do you still have an instance where this is reproducible? Otherwise I would close this, because we can't reproduce it locally. Also fixing symptoms is not that good. |
|
No response yet and this doesn't seem to be reproucible -> closing |
|
@icewind1991 feel free to reopen once you know more about this issue 😉 |
feat: lowercase headers to exclude in exapp proxy
cc @blizzz