Questions about show-remnants and LDAP users

ℹ️ Support
1

Hi all, I have nextcloud 11.0.3 wih LDAP app configured and working.
I read the documentation about removing domain users from nextcloud.

I whish to summurize the parameters involved in user cleanup.

  1. LDAP cache time to live
    immagine

In this example, after 10 minuts (600 seconds), nextcloud will sync LDAP.
Considering in your AD you have the group ‘cloudusers’ and you removed ‘test1’ from it.
Now test1 can’t login anymore.

  1. CRON

immagine

Even if you set 600 second in the ldap, you probably have to wait till cron gest’ triggered.
In such screenshot, it’s set to 15 minutes.

At this point, user test1 shoud be marked as deleted.
It’s file and database entries has not been deleted yet.

  1. ldapUserCleanupInterval

In config.php you have to set the interval for the cleanup, i.e.
‘ldapUserCleanupInterval’ => ‘30’,

So I wonder if cron.php has to be triggered 3 times:

  • sync ldpap
  • mark user as delete
  • delete the user
2

Second question: in config.php shall it write
'ldapUserCleanupInterval' => 30,
or
'ldapUserCleanupInterval' => '30',

Thank you.

3

I answer my self abouth the right syntax.
From ./core/doc/admin/_sources/configuration_server/config_sample_php_parameters.txt

    'ldapUserCleanupInterval' => 51,

defines the interval in minutes for the background job that checks user
existence and marks them as ready to be cleaned up. The number is always
minutes. Setting it to 0 disables the feature.

See command line (occ) methods ldap:show-remnants and user:delete

Defaults to 51 minutes

So the right syntax is without ’ ’

4

Also in ./config/config.sample.php

/**
 * defines the interval in minutes for the background job that checks user
 * existence and marks them as ready to be cleaned up. The number is always
 * minutes. Setting it to 0 disables the feature.
 * See command line (occ) methods ``ldap:show-remnants`` and ``user:delete``
 */
'ldapUserCleanupInterval' => 51,