Bug or feature?

[LilMoke]

Issue Description

From our iOS App we are using this call to log in a user:

PFUser.logInWithUsername(inBackground: userEmail, password: userPassword)

But if the user enters their userEmail with a different case it fails to log in. So is this a bug or is there a way to turn of case sensitive compare for the login? It would be good if I could pass a case flag of something but I do not see a part for that.

Steps to reproduce

Create a user, for example: MyNewUser@Yahoo.com then try to log in and enter mynewuser@yahoo.com and it fails to log in.

Expected Results

Actual Outcome

Environment Setup

• Server

  • parse-server version (Be specific! Don't say 'latest'.) : [FILL THIS OUT]
  • Operating System: [FILL THIS OUT]
  • Hardware: [FILL THIS OUT]
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]

• Database

  • MongoDB version: [FILL THIS OUT]
  • Storage engine: [FILL THIS OUT]
  • Hardware: [FILL THIS OUT]
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): [FILL THIS OUT]

Logs/Trace

[TomWFox]

Not sure if it is a bug but to avoid this problem you could just have userEmail.lowercased() for user sign up and login to ensure that user emails are always lowercase.

[LilMoke]

Yes, but if I do that I will need to also perform a .lower when the user is created and their email is saved, right? On May 30, 2019, at 3:06 PM, Tom Fox <notifications@github.com<mailto:notifications@github.com>> wrote: Not sure if it is a bug but to avoid this problem you could just have userEmail.lower — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#5626?email_source=notifications&email_token=AJ5GWY5KTEBKDGJGHCHBB7LPYAQR7A5CNFSM4HRH3TVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWTHESI#issuecomment-497447497>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AJ5GWYZOJ5VIXL4NV7WSBJ3PYAQR7ANCNFSM4HRH3TVA>.

[TomWFox]

That’s right, you could do that in a beforeSave trigger on the Parse.User class in your Cloud Code.

[TomWFox]

I think it makes sense to close this as it’s a duplicate of #3990 and is being worked on in #5634.