Was there a recent change that is leading to the influx of generic users named “userN” (where N is some number) on our Discourse instance and if so it possible to disable this? I haven’t been able to find anything in the settings.

We recently stopped using email addresses when generating usernames during SSO. FEATURE: stop using email as source for username and name suggestions for Single Sign On (#14541) committed 01:25PM - 12 Oct 21 UTC (UTC) …

Those accounts might’ve been anonymized at some point in time. [Bild] Anonymizing Users in Discourse megaphoneAnnouncements If you want to permanently remove a user from your community, but also preserve their contributions to Discourse, you can anonymize that …

They’re all new users asking their first question, I don’t think they’ve been anonymized by an admin. Edit: or just new users, not necessarily with a post.

What method are these new users using to sign-up?

I’m not sure, is there somewhere I can check that? It seems all these users have empty username details in the DiscourseConnect SSO section at the bottom of the User Admin page, if that means anything. [image]

Do you have groups with the same names? This sounds similar to [Bild] Username changed after Discourse upgrade support There is likely a group with the name martin. Users and groups cannot share the same name. There was previously a bug which allowed this to happen, but…

There is no group called “user”.

[Bild] kevinherron: It seems all these users have empty username details in the DiscourseConnect SSO section at the bottom of the User Admin page, if that means anything. Can you check your discourse connect sign-up and see if the username field can be skipped when registering?

I’ll have to check with the internal systems team that manages our global user accounts and I assume the integration with Discourse Connect SSO. I suspect the issue is somewhere in here… just not sure why the sudden behavior change. I don’t think our global accounts have usernames, just emails, but …

So if our user accounts don’t have usernames and we just supply the email address in the username field of the SSO payload it will behave as it did previously?

[Bild] kevinherron: So if our user accounts don’t have usernames and we just supply the email address in the username field of the SSO payload it will behave as it did previously? Yes, that should work. But it’s better to avoid generating usernames from emails because in this case, it’s easy …

Generische „userN“-Benutzernamen

Unterstützung

JammyDodger 27. Oktober 2021 um 11:48 8

Könntest du bitte deine DiscourseConnect-Anmeldung prüfen und sehen, ob das Feld für den Benutzernamen bei der Registrierung übersprungen werden kann?

Thema		Antworten	Aufrufe
Usernames getting modified – numeral "1" being added SSO	5	1347	12. September 2018
Bad automatic choosing of username when using SSO (DiscourseConnect) SSO	2	847	18. August 2022
Anonymise all users by default during sign up Support	4	325	18. November 2024
Can usernames be numbers instead of Letters? Support	7	2375	7. Januar 2022
Usernames suddenly have 1 appended to end Support	4	496	14. September 2018

Generische „userN“-Benutzernamen

Verwandte Themen