I have entered all the data in the backend. Verify database connection says OK.
But the user data from Nextcloud is not synchronised into the external database (Nextcloud always wins selected).
Is there a trigger for the synchronisation?
If Iâm understanding the question right, youâve created a user account in Nextcloud, then hooked up the âuser_sqlâ integration, and you want your user info to be moved into that database now.
Based on what Iâve seen of the user auth backend integrations like this, I think youâll need to create a new user account now that the integration is hooked up. If you want it to have the same name, youâll need to delete your account and re-create it.
As far as Iâm aware, there isnât a mechanism for moving âNextcloud-nativeâ accounts into the backend, and if an account name exists in both databases, Nextcloudâs own will take priority.
If it helps any, the new user migration feature in NC24 might make it much simpler to move your settings to the new account than it used to be.
The problem is a bit more complex: The problem is that I want to maintain a larger number of users both in a WordPress instance and in Nextcloud. In order to keep the data consistent, I want to maintain it in a database separate from both systems, which is then synchronised with both WordPress and Nextcloud. This process does not have to run continuously, but could also be triggered by the admin as needed.
I understand the description of the app âUser and Group SQL Backendsâ to mean that it could solve the problem for Nextcloud. However, I cannot find a way to trigger the synchronisation.
Hmm, I donât see much documentation around, so Iâll refer to the readme file. If anyone around here knows better, please do correct me. 
There are definitely some things that sync. From the looks of the Options table, that includes name, email, and quota. Thereâs also a cache you can clear, but I donât think that applies to synced items.
If Iâm reading the descriptions of the way the users table should be laid out right, the âuser backendâ is one service provided by this plugin, while sync for the listed 3 things are separate, optional services. I donât see anything about configuring sync for the user backend, so I think thatâs more or less live (apart from caching), as opposed to synced.
I think you set this up, have someone try signing in, and if their account doesnât already exist in the Nextcloud database, then it authenticates them against the password in the backend database. It optionally syncs name, email and quota from there to Nextcloud, but since thereâs nothing here about scheduling, that sync might be triggered by login as well. Might be synced rather than retrieved live to cut down on unnecessary latency.