owncloud / owncloud/user_ldap

Owncloud 9.0 and user_ldap regression (ldap server crash)

Open
#4 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
17
Forks
19
Avg merge
11h 40m
Merged PRs (30d)
2

Description

Original issue in https://github.com/owncloud/core/issues/23619 by @tdesloovere

we upgraded our Owncloud 8.2 server recently to Owncloud 9.0 and noticed a regression regarding the user_ldap app.

Our current setup:
We currently have a Novell Open Enterprise Server which (OES 2015) handles the LDAP requests. Once the LDAP settings are set, we get after the test-configuration more than 1000 entries back. This was working fine in version 8.2 and we could see all the users and groups and scroll through the list of users.

Now we upgraded to version 9.0. Users and groups were still available but when we scrolled through the list of users, Owncloud made our LDAP service on the OES server crash. After some investigation we noticed that it has something to do with paged results settings, if the app finds more than 1000 entries. Less entries, will NOT generate this crash. It looks like version 9.0 generates LDAP-queries that will clash with certain servers.
If we completely disabled paged results on the OES server, the error does no longer appear. Is there a way to disable paged results queries on the Owncloud server (setting to 0 does not work!) ?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the user_ldap paged-results configuration and the test-configuration flow described in the report. Reproduce the behavior with more than 1,000 LDAP entries against Novell OES 2015, comparing paged results enabled and disabled. Done means identifying a working configuration or confirming the incompatibility and documenting the result.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.