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. https://github.com/discourse/discourse/commit/88ecb83382e4dc5cec1d9599619a6c40a07825ae The recommended solution is to supply a username in the SSO payload. You can go back to the previous behaviour by changing a hidden…

Those accounts might’ve been anonymized at some point in time. [圖片] 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 us…

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 [圖片] 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…

There is no group called “user”.

[圖片] 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?

[圖片] 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 to…

通用的“userN”用户名

支持

anon73664359 2021年十月27日 11:01 2

这些账户可能曾在某个时间点被匿名化。

話題		回覆	觀看
Usernames getting modified – numeral "1" being added SSO	4	1407	2018年九月11日
Bad automatic choosing of username when using SSO (DiscourseConnect) SSO	1	904	2022年八月18日
Anonymise all users by default during sign up Support	4	398	2024年十一月18日
Can usernames be numbers instead of Letters? Support	7	2503	2022年一月7日
Usernames suddenly have 1 appended to end Support	3	543	2018年八月15日

通用的“userN”用户名

相關主題