UX: The username suggestion is invalid

[ralgozino]

When creating a new user in Permission Manager, the username field suggests as an example Jane Doe, but if you write that you get an error message saying that the username is not valid:

[ralgozino]

also, "[...] dots and dashes and numbers" shuold be "[...] dots, dashes and numbers"

[RhnSharma]

I would like to take this one.

[ralgozino]

The PR didn't fix the issue. The placeholder problem is still present.

[angelbarrera92]

I think the problem is not only about the tooltip or the placeholder:

1st issue: The place holder "Jane Doe" is an invalid username. Consider using a valid one like: jane.doe.
2nd issue: The validation is incorrect. Backend and frontend are not checking the same regex pattern. In addition, the tooltip is incorrect right now.

Frontend:

    if (
      !username.match(/^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*)$/)) {
      setUsernameError(`user can only contain lowercase letters, dots, dashes and numbers`)
      return false
    }

Backend:

const validUsernameRegex = "^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$"

var invalidUsernameError = `username must be DNS-1123 compliant, it must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'gino.mycompany', regex used for validation is ` + validUsernameRegex

func isValidUsername(username string) (valid bool) {
	re := regexp.MustCompile(validUsernameRegex)
	return re.MatchString(username)
}

We must align these patterns

[divanikus]

For some reason it doesn't accept names with dot in the middle, despite of tooltip saying jane.doe is allowed.

Running latest v1.7.1-rc1

[DesSolo]

#182