Users are experiencing an issue where usernames in Discourse are being modified with a numeral “1” (or higher) when logging in via SSO, and this change toggles on and off with each login. Christian_Suntay reports that the behavior is inconsistent—“1” appears initially but disappears upon re-login, and existing “1” suffixes increment to “2”. codinghorror suggests the issue likely stems from a flawed SSO implementation, where login requests are mistakenly treated as new user registrations. Falco emphasizes that the external_id sent during SSO must be a stable, unique identifier for each user and advises enabling verbose SSO logging to diagnose the problem. Christian_Suntay confirms the inconsistent behavior, indicating a flaky SSO service.
but the thing is the additional “1” is being on/off as you logged in/out and for those usernames with 1 already at the end of the username will be iterated to 2.
yes we are using SSO. but we are using the same email when using the SSO and the username in discourse will have “1” or being iterated if there is already a 1 in their username. In above attached thread it was a bug and was fixed. Maybe it happened again?
It’s more likely something is wrong with your SSO implementation – it sounds like “log me in again as user X!” is instead coming across as “create me as a new user with the name X!” so I suggest double and triple checking the SSO documentation and your implementation of it.
You can also turn on verbose SSO logging in your site settings as I recall.
the problem now is when I logged in for the first time it will have “1” but when I relogged in. it was gone and back to original. It is like an on / off switch whenever I tried to logged in.