Rüdiger Kupper
Rüdiger Kupper
Further information: The wrong user is an LDAP user. "teachers" is an LDAP group.
I don't believe the user actually gained administrator privileges, but the log entries are wrong.
Don't know if it's related. I see regular messages like this in the log: ``` {"reqId":"JP2c5vxUZqDgWTJ1knNb","level":2,"time":"2022-03-24T10:20:23+00:00","remoteAddr":"","user":"--","app":"files","method":"","url":"--","message":"User kup still has unscanned files after running background scan, background scan might be stopped...
Like e.g. ``` {"reqId":"q8rZFdpAZScNfmpqtj2g","level":2,"time":"2022-03-27T21:32:15+00:00","remoteAddr":"","user":"","app":"files","method":"","url":"--","message":"User kup still has unscanned files after running background scan, background scan might be stopped prematurely","userAgent":"--","version":"22.2.5.1"} ``` Looks like the same message, but user keeps changing between...
Just a very wild guess: Do administrators usually get listed at the very front of the user list? Somehow, the alphabetically first user keeps dropping in for "administrator".
More wild guessing: The problem could be in the LDAP interface. All of our ~1000 users get imported through LDAP. There are just two users in the local database: one...
Most probably the regular cron job.
Looks similar, at least. I'll check our oc_activity table and see if it has similar messages.
> Edit: Nevermind, this didn't solve the problem. Pity :-). The problem is unchanged in our install, users still sporadically receive confusing messages from Nextcloud.