Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] Invalid domain part allowed in email during Registration #918

Open
johnson-oragui opened this issue Aug 21, 2024 · 0 comments · Fixed by #924
Open

[FIX] Invalid domain part allowed in email during Registration #918

johnson-oragui opened this issue Aug 21, 2024 · 0 comments · Fixed by #924
Assignees

Comments

@johnson-oragui
Copy link
Collaborator

johnson-oragui commented Aug 21, 2024

Describe the bug
During user registration, the local part of the email is properly validated, as well as the domain part, but any extra character addition to the domain part is allowed(not properly validated) for example [email protected] is currently allowed.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://staging.api-python.boilerplate.hng.tech/register'
  2. Enter your details
  3. Add an extra '.com' to the domain part as many times
  4. Click on register
  5. Registration is successful

Expected behavior
The server is supposed to respond with "Invalid email" or a message of the same likeness.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Browser chrome
  • Version 22

ENTERED [email protected] DURING REGISTRATION
bug register

SERVER ALLOWED REGISTRATION
bug register allowed invalid email

Additional context
The backend should not allow such invalid emails to be registered in the platform

@johnson-oragui johnson-oragui self-assigned this Aug 21, 2024
@johnson-oragui johnson-oragui linked a pull request Aug 22, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant