I have users that register email addresses with of without capital letters in. When these users login from their mobile and they by accident do or do not add this capital and the validation set on field is email, they cannot login. Is there way on login with security server connect to add the function to convert both input field and the server field to lowercase before comparing for login validation?
There are data formatters for to lowercase that you would probably need to use in both the registration process as well as the login process, to make sure they always are lowercase and always work correctly.
In the Server Connect > Security Login > Login Properties make sure you have the Username and Password both set with that data formatter I think it is
Although if you are using encryption I am not sure if that will mess anything up, maybe put your lowercase before it though.
If you are using mysql, you could also create a trigger that would update automatically when people register:
CREATE TRIGGER lowercase_insert BEFORE INSERT ON users FOR EACH ROW SET NEW.username= LOWER(NEW.username); CREATE TRIGGER lowercase_update BEFORE UPDATE ON users FOR EACH ROW SET NEW.username= LOWER(NEW.username);
Then just update everything in the table:
UPDATE users SET username = LOWER(username);
Assuming table is users and username field is username.
Paul I created the login form from your video(thank you for taking the time to do that), I’m having the same issue with username, I’m using an email address in my case as the username. A usernname should not be case sensitive like a password, I’m my case I receive lists with email addresses all in lowercase or upper lower, most do not remember if they used upper or lower case characters when they registered so if they receive a login not correct, most would not know that it’s because of a casing issues, they just think they are positive that’s the email address they used.
I’m using dreamweaver in the past to create login forms I never had to worry about usernames/email being case sensitive, is there a way with wappler handling this without having to reformat the actual data?
It is a problem unfortunately in my opinion.
Lets say you have a situation where your username field in your database has eMaiL@SiTe.cOm or something like that, then that is what the security provider has to exactly match.
What I would do at this stage is go to the form where the users register to become a user and on the input the use to type their username, make it convert to lowercase when inserting to your database.
Can be added to the value of the server connect inset step.
Then on your login page use the data formatters to convert whatever is typed in the username field to lowercase when it reads from the security provider.
Can be added to the Security Login steps Username field
These two procedures will ensure all usernames stored and queried will always be inserted and queried in lowercase from this point forward.
To fix your existing data, go to your existing database and run a sql command on the username column to convert all entries to only lowercase only.
UPDATE usertable SET usernamecol = LOWER(usernamecol);
Can use something like phpMyAdmin to run this.
After all these steps are done you should never really face these issues again.
Hope that helps.
Yes, what you’re saying would solve the issue. However it seems like a bandaid to the actual issue which is the login username with wappler, hoping they put in a fix. The great thing about wappler is that it’s supposed to be a time saving tool, hate to keep having to add extra steps to make things work they way they should that’s all.
To be very honest I do not really see this as a bug, as far as I am aware SQL has been case reliant for many years now if your table is utf8. Although I do not know all that much about it.
In my opinion, if anything, if the Dreamweaver DMX tools do not impose this limitation on login forms, I would personally see that as more of a bug, than the Wappler version that is case reliant.
@Teodor or maybe @Hyperbytes, @TomD, @ben would probably have better insights though in this case.
Basic rule i always consider usernames should NOT be case sensitive, passwords should.
As email addresses are by definition not case sensitive then if they are used as a login they should not be treat as case sensitive,
Other username such as “brian” or “Paul”, that is a design decision for the developer, personally i would not make them case sensitive but I accept that it adds a degree of security
Personally i think the security provider should cater for that but that is only my opinion.