[Logic bug] User creation username
Closed this issue · 3 comments
User create ask you about a username + an email address
But the username field displays an error asking for the username to be an email address, which make username = email.
Option 1
Allow username to be a real username and being able to login either with username or email address.
Option n°2
Keep email only for login but authorize any text in the username field just for display in the app. And actually check the email and not the username in this case.
Notes
It's just a client side check where the username field has type="email"
so I was able to bypass it but then I can't login.
If I try email + password it fails like if the combo was invalid:
I guess it's because it actually checks the username field and not the email one but since in the registration form it forces you to have username to have an email format it make it transparent afterward.
The login form also has type="email"
we can remove it too. So if I just remove the client side requirement I can put my username since it's that it seems to check.
This time I don't have the Login Failed. Incorrect username or password
error but I'm not logged in either. There is maybe a check somewhere in the backend that check that the username has a email format and silently fails.
I have confirmed that the login page actually check the username and not the email address by creating a user with test1@test.local
as username and test2@test.local
as email and successfully logging in with test1@test.local
.
Hi @noraj ,
I've reviewed the issue the login page check the email but the login form validation was not working properly.
Also we deleted the username option in the registration form we will use the email field for both username & email
If you have any doubts do not hesitate to contact me :)
Best regards
Sounds good, I'll try again later.