Repository navigation
Sharing with LDAP Users not working on subsequent attempts when cache is enabled #21896
Description
Steps to reproduce
- Having cache enabled: APCu 4.0.7, Redis 2.2.7
- Trying to share some files/folders with an LDAP User
- When typing the first letters of the Username, User is being correctly found on the first attempt
- However, when deleting the letters and searching again for the same User, this cannot be found and the search seems to be stuck
- This only happens when cache is enabled
Expected behaviour
LDAP User should also be found on the second attempt
Actual behaviour
See above
Server configuration
Operating system:
Debian Jessie
Web server:
Apache 2.4
Database:
Percona XtraDB 5.6.27
PHP version:
5.6
ownCloud version: (see ownCloud admin page)
8.2.2
Updated from an older ownCloud or fresh install:
Fresh install
Are you using external storage, if yes which one: local/smb/sftp/...
local
Are you using encryption: yes/no
no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
LDAP
@MorrisJobke can you maybe help here?
00004656
Activity
MorrisJobke commentedon Jan 27, 2016
Tested on master with APCu 4.0.8 - can't reproduce. I will retry with 8.2.2
MorrisJobke commentedon Jan 27, 2016
Same on v8.2.2 - it works just fine.
I use PHP 5.6.17.
MorrisJobke commentedon Jan 27, 2016
Oh ... I just noticed that it breaks now. I will debug it.
MorrisJobke commentedon Jan 27, 2016
I suspect that there is a problem with the caching mechanism in LDAP.
I noticed that it always fails if I enter the same search term the second time:
User: "Heather,..."
I debugged this a bit, but can't find anything suspicious. The cache key looks good - maybe APCu returns something wrong? @blizzz Can you have a look? You know better what you cached how.
blizzz commentedon Jan 29, 2016
@MorrisJobke I can confirm on master. Did you verify it on 8.2?
The problem is, when reading the after reading the value from the cache and unserializing it, it is turned into a stdClass instance instead of an associative array.
json_decode transforms this into an stdClass:
{"zombie_1102":"Neugebauer, Hassan","zombie_946670":"Neugebauer, Bekir"}Please test the fix: #21998
[user_ldap] properly decode cached objects
MorrisJobke commentedon Jan 29, 2016
Just to update everybody: #21999 contains the fix.
[user_ldap] properly decode cached objects
blizzz commentedon Feb 1, 2016
@nickvergessen you reopened because 8.2?
nickvergessen commentedon Feb 1, 2016
yes
MorrisJobke commentedon Feb 1, 2016
Not really needed. I track the backport PR usually. ;)
[user_ldap] properly decode cached objects
lock commentedon Aug 6, 2019
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.