WB 2.8.2 usernames including "." disallowed?!

[Scone Top]

I just installed WB 2.8.2 in my test environment...

Attempted to creater my first Username...  and was met with this error message...
        "Invalid chars for username found / The username you entered was too short"
The username did include a "." (dot/period/fullstop), well two actually.  This kind of username has been working fine with WB 2.8.1.

Considering our local security policy requirements to use amix of alpha/numeric/non-alphanumeric chars in usernames (as well as passwords)...

Why so strict? 
What can be done to allow "." characters in WB usernames?

This could be a show stopper for my planned seamless WB upgrade on a medium sized Intranet site...

Many thanks in anticipation,
-- Scone Top.

[BlackBird]

In WB 2.8.2, there's a regexp checking usernames:

/^[a-z]{1}[a-z0-9_-]{2,}$/i

This means:

* Must begin with at least one letter (^[a-z]{1})
* Can contain any number > 2 of a-z, 0-9, Underscores and Hyphens ([a-z0-9_-]{2,})

No other chars - including . and @ (if you'd like to use mail addresses as usernames) - are allowed.

See admins/users/save.php

[Argos]

What a ridicilous change! I just upgraded a client site from 2.8.1 to 2.8.2 and also get this error. This means that the policy of creating usernames of my client cannot be continued because of this weird change in WB. I'm really getting frustrated by the silly "security" changes in WB lately. What's the next idea to decrease usability??

I tried to add the @ and . to the pregmatch thingy, but that didn't work. Only removing the pregmatch code helped.

[BlackBird]

This pattern should work.

/^[a-z]{1}[a-z0-9@\._-]{2,}$/i

* Must begin with at least one letter (^[a-z]{1})
* Can contain any number > 2 of a-z, 0-9, Underscores, Hyphens, Dots and @ ([a-z0-9@\._-]{2,})