The discussion revolves around an issue with Discord Login auth not updating usernames correctly in Discourse. AEW745 reported that instead of using the Discord nickname, the system uses the Discord username and changes the username to a default value, such as “User1”. Andreas_Reichmann noted that Discourse usernames cannot contain spaces or special characters, which may be contributing to the issue. Meanwhile, pmusaraj suggested a potential fix, referencing a GitHub pull request that pulls the name from Discord if available, defaulting to the username if it is empty.
Hello, currently logging in with Discord Auth with Auth overrides username and auth overrides name enabled. The name is supposed to be Discord nickname. However, it puts Discord username as the name and changes username to User1 instead of the actual username.
Here is a video to show an example of the bug.
Note that the Discourse username must not contain spaces or special characters.
I had an SSO connection that had been running for some time (with an @ in the username). After one of the recent updates, this ceased to function. I replaced the @ with an underscore, and everything has been working since.
Manually entering an @ in the username is also not permitted in Discourse.
Can you see if this fixes the issue: DEV: Fix username/name mapping for Discord auth by pmusaraj · Pull Request #31494 · discourse/discourse · GitHub? It should pull the name if available from Discord, and default back to the username if it is empty. We could likely make this smarter and only set the name if/when necessary, but the current approach at least doesn’t change existing functionality for users with no display name in Discord.
This topic was automatically closed after 12 days. New replies are no longer allowed.