Skip to content
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

[Bug]: After removing a user with occ, some of its related data remains in DB table oc_notifications_settings #1572

Closed
oleole39 opened this issue Jun 7, 2023 · 0 comments · Fixed by #1583

Comments

@oleole39
Copy link

oleole39 commented Jun 7, 2023

Hello,

Using Nextcloud 26.0.2 (Yunohost package, but it seems not to be limited to that very package), when deleting a user using occ, I notice that if most of that user data is deleted as expected, some do remains (neither particularly heavy nor sensitve data, but still...) in the following tables

Steps to reproduce

  1. Create a user testuser
  2. Associate an email account to it in Nextcloud Mail app (that may be an optional step)
  3. Delete the user using occ user:delete testuser
  4. Check mentioned MySQL table to see whether data related to testuser still remain in there.

Expected behaviour

I guess all data related to the deleted user should be removed (or at least that there an option is provided to do so)

Actual behaviour

A few references to testuser remains in the table oc_notifications_settings in particular (as far as Nextcloud notifications app seems to be concerned)

Server configuration

Operating system:
Debian Bulleye

Web server:
Nginx

Database:
MariaDB 10.5

PHP version:
8.1

Nextcloud version: (see Nextcloud admin page)
26.02

Where did you install Nextcloud from:
Yunohost

Nextcloud configuration:

{
    "system": {
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "localhost",
            "mydomain.tld"
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "mysql",
        "version": "25.0.6.1",
        "overwrite.cli.url": "https:\/\/mydomain.tld",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "mysql.utf8mb4": true,
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory",
        "updatechecker": false,
        "memcache.local": "\\OC\\Memcache\\APCu",
        "integrity.check.disabled": true,
        "filelocking.enabled": true,
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "port": "5555",
            "timeout": "0.0",
            "password": "***REMOVED SENSITIVE VALUE***"
        },
        "hashing_default_password": true,
        "localstorage.allowsymlinks": true,
        "simpleSignUpLink.shown": false,
        "logout_url": "https:\/\/mydomain.tld\/yunohost\/sso\/?action=logout",
        "maintenance": false,
        "loglevel": 2
    }
}

Are you using an external user-backend, if yes which one: LDAP & SSO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant