incompatibility between Circles/Collectives and Backend Primary Object Storage (S3/Swift)

perpetual App error "FederatedUser is not complete in nextcloud/apps/circles/lib/Service/FederatedUserService.php in line 1086". When creating a user, or creating collectives.

Steps to reproduce the behavior:

Configure Backend Storage Object Store in config.php : Array(Class=>"\OC\Files\ObjectStore\S3")

Install and enable the following apps on your nextcloud instance:

files_versions
viewer
text
circles

Then install and enable "Circles" &"Collectives" app.

The error already shows up at this stage in file nextcloud.log.

Go to 'Collectives icon'
Click on 'Add New Collective'
Follow the creation instructions
See the pop up error message coming up

Expected behavior A clear and concise description of what you expected to happen.

Whenever we try to create a user (occ CLI, admin web interface or registration form), the error is shown but user is created correctly. Whenever we disable circles app, the error is not here anymore.

Server details:

Collectives app version: [2.9.2]
Circles app version: [25.0.0]
Nextcloud versions: [26.0.11] & [25.0.7/25.0.13]
PHP Version: [8.1.20]
Database: [postgreSQL 11.10]

Client details:

OS: [Windows]
Browser: [Firefox]
Browser version: [115.3.1]

Is Circles (and/or Collectives) App(s) compatible with Primary Backend Object Storage (S3/Swift) ?

We suspect that the "FederatedUser: is not complete" error is linked with primary backend object storage configuration. Since the circles/collective applications rely on a hidden subdirectory in the user folder _/var/www/html/data/_, that in the collective configuration mentions the "types" attribute refers to "filesystems" and that in the context of Primary Backend Object Storage, those user directories do not exist.

occ config:list collectives
{
    "apps": {
        "collectives": {
            "installed_version": "2.9.2",
            "types": "filesystem",
            "enabled": "yes",
            "debug_level": "0"
        }
    }
}

Since these applications are based on a Filesystem subdirectory trees, wouldn't it be a good idea to set up a specific external storage for these Circles/Collectives applications? Would it be possible and usable ?

nextcloud / circles

incompatibility between Circles/Collectives and Backend Primary Object Storage (S3/Swift) #1516