You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally, when a user is being disabled or enabled, a UserChangedEvent is being emitted. There are listeners that consume this change. One example is the dav app, which updates the system addressbook and removes disabled users and re-add re-enabled users.
Now when the LDAP configuration's setting markRemnantsAsDisabled is set to 1 then all remnants users are reported as disabled, but the event is not being emitted at any time. And so components that act on stored information, like the system addressbook, do not have the information and still show that user in the contactsmenu.
Steps to reproduce
Have an LDAP confguration
Modify the config per cli (it is not exposed so far): occ ldap:set-config s01 markRemnantsAsDisabled 1
Delete a users on LDAP
Ensure the user is known as deleted: occ ldap:check-user $USERID
In the web interface, look in the contacts menu for this user
Expected behavior
The user does not show up in the results
Installation method
None
Nextcloud Server version
master
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Default user-backend (database)
LDAP/ Active Directory
SSO - SAML
Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
Affected are 28-master
The text was updated successfully, but these errors were encountered:
Latest idea: run triggerChange() from the private user instance on DeletedUsersIndex::markUser() and OfflineUser::unmark(), when the setting is enabled. Perhaps also register a background job to run this events when enabling this setting (and vice versa).
Bug description
Normally, when a user is being disabled or enabled, a
UserChangedEvent
is being emitted. There are listeners that consume this change. One example is the dav app, which updates the system addressbook and removes disabled users and re-add re-enabled users.Now when the LDAP configuration's setting markRemnantsAsDisabled is set to 1 then all remnants users are reported as disabled, but the event is not being emitted at any time. And so components that act on stored information, like the system addressbook, do not have the information and still show that user in the contactsmenu.
Steps to reproduce
occ ldap:set-config s01 markRemnantsAsDisabled 1
occ ldap:check-user $USERID
Expected behavior
The user does not show up in the results
Installation method
None
Nextcloud Server version
master
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
Affected are 28-master
The text was updated successfully, but these errors were encountered: