I found a similar thread to the issue I’ve just experienced.
In the settings,
reserved usernames was set to disallow a specific prefix for users. It was only two letters but they are the abbreviation of a client’s company name, which for this purpose I’ll call
AB*. This was put in place in May 2020 according to the logs.
But a user has registered recently (3 days ago) with a name of
Absupport (note the lower case “B” compared to the reserved list).
Does casing make a difference here? I obviously thought the wildcard would have prevented this, but it didn’t. It did silence the user because they typed too fast, but I would have expected the username to not have been registered at all. Or am I misunderstanding it?
Any input/guidance appreciated.