VERY VERY IMPORTANT !!!
I identified a situation that is very 'interesting' and relevant(!) to be pointed and discussed: Email authentication is case sensitive and from a security perspective it is obviously very good, the users table the field email is unique and case sensitive too and again from a security standpoint it's obviously very good. Having said that I tested and verified that you can create a new user account with these emails as examples: [email protected], another: [email protected], another: [email protected] ....and so on... which in prism of registration of users and database consistency is possible to generate a HUGE PROBLEM 💣; Imagine one user that didn't notice and typed an upper or lower case character (or forgot), he will try to login, a message will rise: non-existent account 🤔, and he can/will create another account💡 believing countless things that passes in his mind ... here the mess 💩 🤣 is done, database having two or more accounts from the same person with 'same' email (only with characters cases variations) !!! From my humble point of view this is TERRIBLE! 😱 🤕 😪
Below I show what I did to avoid this, but I would like to suggest if it makes logical sense to have something native in Xano, or in the default CRUD API's that are created with a new instance already have this setup I made ( or similar ) by default and/or in the documentation to have one clear instruction in this regard.
Let's brain storm this:
  and Â
So far what I did was:
1) Signup process when I add new user, I used filter 'to_lower' to email input value.
[image.png]
2) Login process at get user record Find users record by field email, I also added 'to_lower' filter to email input value.
[image.png] 
