The user sync cron job is an additional cron job inside the docker container, which is independent of the cron.php cronjob.
I just noticed that by default the installed cron job only disables no longer existing ldap users in ownCloud. Probably because the default behavior when removing a user is to automatically remove all their files.
So you have a few options now:
- Edit the cronjob directly, by logging in via SSH to the appliance, docker exec into the container and edit the file
/etc/cron.d/sync, where you replace disable with remove. This has the downside, that when the container gets updated the cronjob will be replaced with the default cron job again.
- You install the following cronjob on the Appliance server (docker host) with the command
crontab -e while logged in as root:
*/10 * * * * univention-app shell owncloud occ user:sync -m remove 'OCA\User_LDAP\User_Proxy' This has the advantage that this should also work after an ownCloud upgrade.
- You manually run the command
univention-app shell owncloud occ user:sync -m remove 'OCA\User_LDAP\User_Proxy' whenever you actually want to remove users in ownCloud (and all their files) that have been removed from the LDAP backend.