Skip to content

Conversation

@icewind1991
Copy link
Member

cc @blizzz

@icewind1991 icewind1991 added the 3. to review Waiting for reviews label Jul 26, 2016
@icewind1991 icewind1991 added this to the Nextcloud 11.0 milestone Jul 26, 2016
@mention-bot
Copy link

@icewind1991, thanks for your PR! By analyzing the annotation information on this pull request, we identified @blizzz, @MorrisJobke and @dschmidt to be potential reviewers

@MorrisJobke
Copy link
Member

The login works for me even without this change. Could you please comment what this change will address?

@icewind1991
Copy link
Member Author

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) $user ends up being null which currently breaks login

@MorrisJobke
Copy link
Member

@blizzz Any comment on this?

@blizzz
Copy link
Member

blizzz commented Aug 19, 2016

I am bewildered, need to verify.

@blizzz
Copy link
Member

blizzz commented Aug 19, 2016

@icewind1991 I cannot verify the issue

$ cadaver http://nc.zara/master/remote.php/webdav
Authentication required for Nextcloud on server `nc.zara':
Username: master
Password: 
dav:/master/remote.php/webdav/> ls
Listing collection `/master/remote.php/webdav/': succeeded.
        welcome.txt                          164  Aug 19 12:26

do you have detailed reproduction steps?

@icewind1991
Copy link
Member Author

No, it probably depends on the specific ldap setup but I don't have enough ldap knowledge to know why

@blizzz
Copy link
Member

blizzz commented Aug 19, 2016

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 No or empty name for $dn) or a new mapping would not succeed (includes trying alternate names), would result in a log line like Could not create unique name for $dn.

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 OCA\User_LDAP\User resulting in just one condition, the effect would be the same however. Typically, the result would be a user one so changing it accordingly might be a bit of micro optimization.

@MorrisJobke
Copy link
Member

@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.

@MorrisJobke
Copy link
Member

No response yet and this doesn't seem to be reproucible -> closing

@MorrisJobke MorrisJobke closed this Sep 6, 2016
@MorrisJobke MorrisJobke deleted the ldab-non-ldab-user branch September 6, 2016 08:28
@MorrisJobke
Copy link
Member

@icewind1991 feel free to reopen once you know more about this issue 😉

R0Wi pushed a commit to R0Wi/server that referenced this pull request Nov 22, 2025
feat: lowercase headers to exclude in exapp proxy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants