Skip to content
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

user_ldap: recommends to have a local proxy cache, but this fails when large numbers are returned #6392

Closed
eigood opened this issue Sep 6, 2017 · 5 comments

Comments

@eigood
Copy link

eigood commented Sep 6, 2017

nextcloud-version: 12.0.2

This is not a pure nextcloud bug. I configured a local openldap proxy around the remote Active Directory. When nextcloud talks to the remote, I get 2957 groups. When it talks to the local slapd, I also get 2957 groups. In both cases, it's doing it $pageSize at a time(500). However, when I enable slapo-pcache, the pageSize value is ignored, and I only get the maximum size allowed by the remote server(2000 in this case).

I'm currently talking with openldap upstream about this, but they seem to think it's an AD bug, and not a pcache bug.

My suggestion for nextcloud is to not recommend pcache until this is fixed, as doing so means that the resultset is truncated. :(

@eigood
Copy link
Author

eigood commented Sep 7, 2017

Ok, good news. openldap upstream has acknowledged the bug, and while it was initially closed, has been re-opened.

Here is the upstream link: https://www.openldap.org/its/index.cgi/Incoming?id=8724

@eigood
Copy link
Author

eigood commented Sep 7, 2017

This is mostly because the pcache example config for nextcloud only specifies a ttl for pcacheTemplate. There are actually additional ttl options to be set( ).

@MorrisJobke
Copy link
Member

This is mostly because the pcache example config for nextcloud only specifies a ttl for pcacheTemplate. There are actually additional ttl options to be set( ).

@nextcloud/ldap What to do here?

@blizzz
Copy link
Member

blizzz commented Nov 24, 2017

Uh, good question. Sounds indeed just like an issue on a 3rdparty and nothing we can do about.

@eigood where did you see the pcache recommendation?

@nextcloud-bot nextcloud-bot added the stale Ticket or PR with no recent activity label Jun 20, 2018
@blizzz
Copy link
Member

blizzz commented Dec 7, 2018

As it is not an issue within Nc directly and I am not aware that we recommend pcache anywhere, I close this issue. If you disagree, we can reopen and discuss…

@blizzz blizzz closed this as completed Dec 7, 2018
@nextcloud-bot nextcloud-bot removed the stale Ticket or PR with no recent activity label Dec 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants