After update the app "LDAP Integration" from version 0.13.0 to 0.14.0 onwcloud client can't sync with my server

Hi, i updated the app “LDAP Integration” from “0.13.0” to “0.14.0” and now i can’t sync owncloud client with my server, when i start the owncloud client gives allways this error:

Server replied “503 Service Unavailable” to “PROPFIND https://MyServerAddress/owncloud/remote.php/webdav/” (Error: Using $this when not in object context)

My system: The currently installed release version is 4.4-2 errata350.
ownCloud Server version: Version 10.2.1-1

Any help for this error?

Edit: I know if reverting from 0.14.0 to 0.13.0 it works but it’s a workaround and not the final solution.

Best regards,
Pedro Roboredo

Hi, i have the same issue, however - can you guide me how to downgrade the LDAP integration as you mention as a solution ?

How to downgrade the LDAP integration as workaround (solution):

1 - Uninstall app “Ldap 0.14.0” thru ownCloud WebGui with Admin privileges
1.1 - Go to “Market”
1.2 - Uninstall app “Ldap 0.14.0”
1.3 - LogOff ownCloud WebGui

At this point you have this error if you try to access ownCloud thru WebBrowser:

"Update needed
Automatic updating is disabled in config.php. To upgrade your instance, please use the command line updater (occ upgrade).

For help, see the documentation."

2 - Go to the UCS command line interface:
2.1 - univention-app shell owncloud
2.2 - su www-data
2.3 - occ maintenance:mode –-on
2.4 - occ upgrade
2.5 - occ maintenance:mode --off
2.6 - exit
2.7 - exit

At this point you have the app “Ldap v0.13.0” installed, no more errors when accessing ownCloud thru webBrowser and now you can sync your files and folders with owncloud client.

Hi,

I did it in a different way …

  1. Stop onwCloud: univention-app stop owncloud
  2. Downloaded the “old” version of LDAP Integration here: https://marketplace.owncloud.com/apps/user_ldap
  3. Copy the file here: /var/lib/univention-appcenter/apps/owncloud/data/custom/
  4. Change directory: cd /var/lib/univention-appcenter/apps/owncloud/data/custom/
  5. Backup directory user_ladap: mv user_ldap /somebackupdir/
  6. Extract/install tar: tar xzf user_ldap-0.13.0.tar.gz
  7. Start ownCloud: univention-app start owncloud

I was just wondering how "occ upgrade (step 2.4)" is able to install the previous version of the plugin - where this is coming from?

So until you downgrade you can not sync your files with the sync client?

Does this problem only appear when syncing LDAP users or local users too?

How did you upgrade the app?

Did you connect your own LDAP or used the one from Univention?

Hi,

seems only LDAP/AD users are affected by this on our system - default (local Admin) ownCloud-account wasn’t affected by this.

First I was affected by this in prod-environment (LDAP/AD enabled environment), testing this in my test-environment (fresh installed virtual environment) gave me the same result.

App was upgraded as described here (via onwCloud-Market): ownCloud webdav access broken since todays update to version 4.4-2 errata350

The leading instance in our environment for user-accounts is AD-based (Windows Server 2016 as PDC), but the ownCloud LDAP Integration plugin is configured to use the local UCS LDAP instance.

Which other univention apps apart form ownCloud have you installed?

Besides ownCloud, only Bareos and Nagios were installed on the test environment.
If needed and helpful, I can provide the steps how I was able to reproduce the issue - just let me know.

Yes, steps to reproduce would be very helpful.

*So until you downgrade you can not sync your files with the sync client?
That’s true.

*Does this problem only appear when syncing LDAP users or local users too?
For local users (i don’t use LDAP users).

*How did you upgrade the app?
Thru ownCloud - Market

*Did you connect your own LDAP or used the one from Univention?
I only use user created inside ownCloud (I don’t use LDAP)

*Which other univention apps apart form ownCloud have you installed?
I only have ownCloud installed and running.

*Yes, steps to reproduce would be very helpful.
My system: The currently installed release version is 4.4-2 errata350.
ownCloud Server version: Version 10.2.1-1
Users: ownCloud users (No LDAP users)
ownCloud Client version: Windows 2.6.0 build 12644

Only one step for me to reproduce this problem:

  • Update “LDAP Integration” from “0.13.0” to “0.14.0” thru ownCloud Market

sure :slight_smile:

I’m not going to much into details … this is what I did (virtual test environment):

  1. Clean UCS Install
  2. Applied all updates (up to errata 350)
  3. Installed ownCloud from app-center (LADP Integration plugin 0.13.0 was installed automatically)
  4. Login into ownCloud as admin (default: owncloud) and configure LDAP connection (user authentication)
  5. Configure ownCloud Windows-Client in order to use this new instance - In my case everything worked as expected now
  6. Login into ownCloud as admin again and update LDAP Integration plugin from ownCloud Market (ver. 0.14.0)
  7. Disconnect ownCloud Windows-Client and try to reconnect again - At this point the connectivity (client -> ownCloud test server) for me was broken
  8. Fallback (manually) to LDAP integration plugin ver. 0.13.0 and repeat test … operation should be back to nomal now.

Could you eventually repeat this with our appliance?

https://appcenter.software-univention.de/univention-apps/current/owncloud/Univention-App-owncloud-virtualbox.ova

In the mean time I try it your way :slight_smile:

Basically you get the same but all pre configured.

Okay, I could reproduce your error. We will look for a solution.

Here is the workaround for now until we fix this issue.

After the upgrade of the user_ldap app

univention-app shell owncloud

rm -rf apps/user_ldap

Then you will be able to connect via sync client to owncloud

Mastodon