OpenID connect doesn't check username on violations. Eg. a username should not contain a comma but those characters aren't checked / replaced.
1. Setup an openID generic
2. Make sure the returned username is something like 'Lastname, Firstname'
3. Login with this account using SSO.
4. The user account is correctly created and username is filled in with the Lastname, firstname format
5. Try to edit the account.
The system will give you an error: "The username contains an illegal character."
Use the preg match replace option to remove any invalid character from the username
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 3294141-3.patch | 839 bytes | jeroent |
| #2 | openid_connect-invalid_username_character-3294141-2.patch | 470 bytes | kevinvb |
Comments
Comment #2
kevinvb commentedProvided a small patch which uses the pattern from the UserNameConstraintValidator.
Suggestions are welcome.
Comment #3
jeroentAnother check that doesn't happen is the username length.
The external login provider I use, uses usernames longer that 60 characters, which results in a fatal error.
Comment #4
sanduhrsClosing this as a duplicate of #3252021: Truncate username if it is greater than 60 characters.