Age | Commit message (Collapse) | Author |
|
In https://github.com/nextcloud/server/pull/28774 we disabled the
caching for the groupfolder application since it worked due to the fact
that in groupfolders, getFileIds could be called with the same $cacheId
and path for actually different groupfolders.
This revert this change and instead add the folderId from the
groupFolder to the cacheId. This solve the issue of the uniqueness of
the cacheId inside GroupFolder. Downside is that we introduce
groupfolder specific implementation inside the server repo.
The seconf optimization is to not consider paths starting with
__groupfolders in executeCheck. This is due to the fact that files in
the groupfolder application call two times executeCheck one time with
the url __groupfolder/<folderId>/<path> and the other time with <path>.
The first time will always return an empty systemTags array while the
second call will return the correct system tags.
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Co-authored-by: Joas Schilling <213943+nickvergessen@users.noreply.github.com>
|
|
It is not possible to drop and create the same table in one migration
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Use a backup table to copy the data, drop table and recreate it with
correct primary key, then copy the data back and drop the backup table.
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
[stable20] Support LDAP dns longer than 255 characters
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
- the issue was present only when using PHP based resolving of nested
group members. Normally nested members are common in AD (and Samba4) and
are resolved per LDAP_MATCHING_RULE_IN_CHAIN by default
- resolving nested members is recursive
- when the cache entry was created it happend for intermediate groups, too,
containing members from the parent group
- the check was added to only cache the root group with its members
- a runtime cache stores intermediate ldap read results
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
The documentation says it can return false, and even if that is highly
unlikely for sha256, better safe than sorry.
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
This is to ensure new installations do not need to go through migration
history.
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
We cannot set ldap_dn_hash column as notnull because it is empty for
existing users before postSchemaChange is called
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Adds an ldap_full_dn column to store the dn, and only store a sha256
hash in the ldap_dn which is shorter and can be indexed without
trouble.
Migration still needs to be implemented.
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|