Steps to reproduce
- Enable Manual File Locking App
- Lock one file using LDAP user
- Try editing the document (using OnlyOffice or download/upload a file or edit the file over desktop client)
I’ve tried this with 3 different ownCloud servers (all different versions), all connecting to different LDAP server as well with 3 different OnlyOffice Docs servers (also different version). I get this error in all cases.
Expected behaviour
LDAP user who locks the file should be able to edit it. This functionality works fine with local owncloud user, but not with LDAP users.
If you open a document in OnlyOffice, it is opened in read-only mode.
If you try to download, edit and then upload the file again, it says the file is locked.
Actual behaviour
No user can edit the locked file. Not even the LDAP user who locked it.
Server configuration
Operating system:
Ubuntu 20.04 LTS
Web server:
Apache
Database:
MariDB
PHP version:
7.4
ownCloud version: (see ownCloud admin page)
Tried on different ownCloud version with also different OnlyOffice versions
10.7 - 10.9
Updated from an older ownCloud or fresh install:
fresh install
Where did you install ownCloud from:
Signing status (ownCloud 9.0 and above):
Login as admin user into your ownCloud and access
http://example.com/index.php/settings/integrity/failed
paste the results into https://gist.github.com/ and puth the link here.
The content of config/config.php:
Log in to the web-UI with an administrator account and click on
'admin' -> 'Generate Config Report' -> 'Download ownCloud config report'
This report includes the config.php settings, the list of activated apps
and other details in a well sanitized form.
or
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your ownCloud installation folder
*ATTENTION:* Do not post your config.php file in public as is. Please use one of the above
methods whenever possible. Both, the generated reports from the web-ui and from occ config:list
consistently remove sensitive data. You still may want to review the report before sending.
If done manually then it is critical for your own privacy to dilligently
remove *all* host names, passwords, usernames, salts and other credentials before posting.
You should assume that attackers find such information and will use them against your systems.
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your ownCloud installation folder.
Are you using external storage, if yes which one: local/smb/sftp/…
Are you using encryption: yes/no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/…
LDAP configuration (delete this part if not used)
With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your ownCloud installation folder
Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM `oc_appconfig` WHERE `appid` = 'user_ldap';
Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.
Client configuration
Browser:
Operating system:
Logs
Web server error log
Insert your webserver log here
ownCloud log (data/owncloud.log)
Insert your ownCloud log here
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...