Hey, we are planning to use Discourse linked with sign in from an outside oauth. The thing is some of our existing users have 2 or more “special” chars in their username and username_no_double_special is trying to remove the extra. So before I hack the forum to bits to remove “username_no_double_sp…

Discourse has fairly strict rules on usernames, I don’t recommend relaxing that as a lot of downstream stuff may break. If you need unicode or other unusual characters, put them in the “Full Name” field – that’s what it is for.

The problem with that (for our use case) is a) we will need to store the username they use to log in with on the site that we will be using for oauth to do other checks down the road. b) as far as I can see discourse allows users to set their “full name”. So even if I force set it during account cr…

We also store external_id for SSO logins, that may help you.

Username_no_double_special Any reason to enforce it?

Development

codinghorror (Jeff Atwood) October 18, 2016, 10:50pm 4

Yes, it is OK to turn off editing of usernames if the SSO scheme requires them to match.

Topic		Replies	Views
Dropped special characters in usernames Product Support	8	2470	February 25, 2020
Any options for over-riding the username restrictions? Product Support	14	4359	September 6, 2018
Change username requirements Product Support	5	1934	March 20, 2015
Change email and username charset to unicode SSO	2	1208	March 9, 2022
Username with Japanese characters appending a number Product Support	4	935	June 12, 2022

Username_no_double_special Any reason to enforce it?

Related topics