-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to delete User_LDAP user files/shares #4117
Comments
I also might have that problem. Checking a user account presence:
Then trying to delete it:
Log excerpt:
The LDAP server is present, however, and LDAP logons possible. |
+1 |
Introduced by #2845 The early fetching of the home directory caused that one property was not set – this happens on |
homesToKill was not set in runtime since some changes some place else. It required deleteUser() to be called first. The method acts independent of it now. Signed-off-by: Arthur Schiwon <[email protected]>
Actually there is a test for it and it's a challenge… |
homesToKill was not set in runtime since some changes some place else. It required deleteUser() to be called first. The method acts independent of it now. Signed-off-by: Arthur Schiwon <[email protected]>
Fix in #5689 |
running into this issue as well. nextcloud logging is constantly outputting errors about deleted ldap users and i have no way to delete them with occ. |
homesToKill was not set in runtime since some changes some place else. It required deleteUser() to be called first. The method acts independent of it now. Signed-off-by: Arthur Schiwon <[email protected]>
|
LDAP: simplify returning the homePath and fixing #4117
homesToKill was not set in runtime since some changes some place else. It required deleteUser() to be called first. The method acts independent of it now. Signed-off-by: Arthur Schiwon <[email protected]>
[stable12] LDAP: simplify returning the homePath and fixing #4117
I'm running into this issue. Setup LDAP which brought in all of my users before i narrowed it down to a group. Wanted to reconfigure the username mapping from UID to sAMAccountName so others could more easily share by searching usernames. Since it imported all of my users, they are already mapped to a UID internally. When I run sudo -u apache php occ ldap:show-remnants it displays all of my users that are no longer in the correct group, but i can't delete them to get them in the correct ad group and map thier UID to username. It just gives me this error [OC\User\NoUserException] v 12.0.3 |
fix in 12.0.4 |
nope..
so the user is still in the database, but i can not find him:
any ideas? |
ok, after a day it show me the user as remnants, and I can delete the user:
How long must be a user deleted to show up as remnants? |
I think this should answer your question. Simply because you deleted the user does not mean Nextcloud has queried your LDAP server...Take a look at this:
Set ldapUserCleanupInterval in config.php to your desired check interval in minutes. The default is 51 minutes. https://docs.nextcloud.com/server/12/admin_manual/configuration_user/user_auth_ldap_cleanup.html |
Steps to reproduce
Expected behaviour
User, his all data and shares removed.
Actual behaviour
User is visible in ldap:show-remnants output.
If LDAP cache is expired and does not contain a deleted user anymore, the user:delete operation fails saying that the user does not exists (while his files and shares are still present). User shares become broken but visible (not able to access them or unshare them)
Server configuration
Operating system: Debian Jessie
Web server: Apache 2.4
Database: Mariadb 10
PHP version: 5.6.27
Nextcloud version: 11.0.2
Updated from an older Nextcloud/ownCloud or fresh install: updated
Where did you install Nextcloud from: updater
Are you using an external user-backend, if yes which one: LDAP
Nextcloud log (data/nextcloud.log)
Nextcloud log
While accessing share of user deleted from ldap:The text was updated successfully, but these errors were encountered: