Hi Tooey,

I could possibly add some web.config setting that would allow you to specify a regex expression and text to display if the regex fails validation. But, the problem is in many cases the userid and the display name are generated. Specifically it is generated for anyone registering with OpenID/RPX/Windows Live and also it is generated if you use this setting:

<add key="AutoGenerateAndHideUserNamesWhenUsingEmailForLogin" value="true" />

This setting reduces registration friction because there is less for the user to fill out to register.

I don't have an easy way to let you control how it is generated so making it match the expression would not be an easy thing to accomplish. Basically it tries to use the first part of the email before the @ sign as the userid and display name, but since it must be unique it checks against the existing users and if needed appends numbers until it finds one that is not in use.

Best,

Joe

Hi Tooey,

I think it would be difficult for you to solve this without modifying mojoportal code.

I would consider making this possible but I'd be interested to know why you want to do it and are you talking about just the login name or just the display name or both. What regex expression would you use for each and why?

To me it seems like adding extra barriers to registration whenever there are extra validations that may confuse or frustrate a user.

Just as a side note, I read a article recently about how poorly written regex expressions can be used for denial of service attacks. Not saying it is a reason not to do it, just an interesting thing to know about and consider when using regex expressions.

Best,

Joe

Hi Tooey,

Can you give a concrete example of a regex expression that would achieve your goal and what text would you want to display if they enter an invalid string?

Would you use the same expression for both userid/login and display name? or would 2 settings be needed?

Best,

Joe

Thanks Tooey,

I'll see what I can do and use your example for testing.

Best,

Joe

I have implemented this, in the coming release of mojoPortal you will have these new settings in Web.config

<add key="UserNameValidationExpression" value="" />
<add key="UserNameValidationWarning" value="User ID must use only alpha numeric characters and underscores" />

You can enter a validation expression and warning message of your choosing.

Best,

Joe