A user, fefrei, is experiencing an issue where they cannot change a username due to SSO being enabled. They receive an error message stating “There was an error changing your username.” codinghorror suggests it may be due to a length restriction. fefrei discovers the issue is caused by the setting “sso overrides username.” They consider this a bug, suggesting that the setting should either hide the “Change Username” button or allow admins to make changes with a warning. andrei finds a PR that adds test cases for this issue and later discovers (andrei) that the issue is already fixed, with the “Change Username” button being hidden when the setting is enabled, and a warning message displayed when an admin attempts to change a username.
When renaming a user (from jb1 to jb), I get this error message:
There was an error changing your username.
No information is recorded in /logs.
The old username was created because the user used SSO for the first time, and his name was too short. Now, I changed the minimum username length, and wanted to adjust his name.
what happens when you rename to jb2 … jx ?
Almost certainly a length restriction. Unlikely to be a bug.
Is there any setting for length restrictions apart from min username length, which I have set to 2?
Setting any other name does not work either.
Changing username minimum after the fact (e.g. setting minimum username length to 4 chars, when you have ten users with 2 char usernames) will cause lots of problems.
what happens if you restart your container, maybe something bad is cached?
I restarted (or in fact: rebuild) the container, this did not help.
I found it: sso overrides username prevents the name change.
I still consider this situation a bug. Enabling this setting should either hide the Change Username button from the administrator panel and disable the users/.../preferences/username page, or still allow username changes for admins (possibly with a warning).
I’d prefer the latter, to allow admins to manually “untangle” cases where Discourse’s change-illegal-names-system has created unintended names.
Questa PR aggiunge casi di test per il problema descritto nell’OP, così da poter essere sicuri che, in generale, la sovrascrittura del nome utente, ad esempio da jb1 a jb, funzioni:
Ci darò un’occhiata.
Si è scoperto che è già stato risolto. Nascondiamo questa matita quando l’impostazione è attiva:
Inoltre, mostriamo questo se un amministratore sta cercando di cambiare il nome utente di un utente:
Questo argomento è stato chiuso automaticamente dopo 5 giorni. Non sono più consentite nuove risposte.
