-
Notifications
You must be signed in to change notification settings - Fork 17
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
Can't delete LDAP users #317
Comments
GitMate.io thinks possibly related issues are #26 (LDAP Plugin stops after Importing first user), #294 (Can't remove LDAP users after removing the LDAP server), #279 (Cannot add a comment containing an emoji when an LDAP user), #224 (Feature: LDAP users could be deleted over the User-Settings-Web-UI), and #198 (avatar is displayed in owncloud after being deleted in LDAP). |
Forget check user for now. In 10 the sync command should detect the missing user and be used to cleanup the user as specified (disbale or delete). |
Shows that the sync command is detecting user1 as not there and is deleteing the user as requested. |
What evidence is there that the user still exists? If after the user sync command saying it is deleting the user the user is still there in the oc_accounts table then we have a bug with the sync command not deleting like it is saying it is.
This looks like a log message produced from running the above occ commands and appears correct since the user is not on ldap anymore (or at least in the search scope). |
Yes, but in the customers environment and in my reproduction of the customers environment after the sync command the user directories are still there, so are the db entries. |
a |
Just delete the folder then if that is all that remains. |
for 200 user? This is exactly what my script would do, with the db tables removal, who are still there. But you, Jörn, Michael were against the script because it's too risky. |
Ah, so there is more than just the data folder - not the impression I got from your answer above. It seems there is a bug in core then, can you confirm the steps so we know we can reproduce:
expected:
actual:
Correct? |
No. A fresh oC 10 does not have this issue. An updated ( from 9.1.5 ) oC has this issue. As stated in my first post in this issue. |
We are facing the same issue and this prevents us to delete more than 400 users, and their respective user homes, that no more exist in LDAP but still alive in DB. |
Steps to reproduce
occ ldap:check-user user1
Expected behavior
Actual behavior
Related issue
owncloud/core#27861
Because of that, I recomended to the customer an upgrade to 9.1.8 or to 10.0.10.
Customer upgraded to 10.0.9 and user:sync finds nothing:
Original Issue of the customer before the upgrade:
Issue reproduction:
I could reproduce this issue. Issue persists on 10.0.10 as well. user:sync finds no removed users and user:remove can not remove the user.
Customer wrote:
Owncloud log does not show errors:
Also
does not help
ldap:check user does still say user should be deleted.
Messages like
{"reqId":"8Ktv03DhKQJ4LBcUDd5v","level":3,"time":"2018-11-23T08:48:18+01:00","remoteAddr":"","user":"--","app":"OC\\Files\\Filesystem","method":"--","url":"--","message":"Backends provided no user object for user1<mailto:user1>"}
are shown in the ownloud log.
The text was updated successfully, but these errors were encountered: