As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
On the iOS SDK it appears that the user name is case sensitive and it should not be. I checked the forums and there was an entry here titled "I think User Discovery should not be case sensitive" (https://support.kinvey.com/support/discussions/topics/5000040933) which has made 3 years ago and there's a comment about making it a feature request, but it appears that feature request has never been implemented.
The log in username should not be case sensitive. For example. if I create an account with a user name of "username@gmail.com" but then try to log in as "UserName@gmail.com" the login will fail because it's doing a case sensitive check of the user name and it should not.
Currently I work around this issue by converting the username to all lowercase when the account is created and when the user tries to log in. Also note that in my situation I use the email address as the username, but I store the email address and username separately. Regardless, user names should never be case sensitive. Only passwords should be case sensitive.
Best Answer
B
Billy Gee
said
about 6 years ago
Hello Xavier,
As Pranav has mentioned, after consulting with Product and Engineering, case sensitive user names were implemented by design. At this point in time there are no plans to change this.
Case sensitive usernames adds a layer of security to credentials and login.
If you have a significant requirement for case in-sensitive usernames, the best way to do it would be for you to implement this on the client side or in Business Logic. A couple of options to do so are as follows.
1) When the user is created, implement Business Logic that automatically converts the username to lowercase.
2) In the client, you can convert the username to lowercase before sending it on login.
We hope that this helps. Please let us know if you have any questions.
We are case sensitive by design but I will discuss this scenario with the backend team and get back to you with more information.
Thanks,
Pranav
Kinvey
B
Billy Gee
said
about 6 years ago
Answer
Hello Xavier,
As Pranav has mentioned, after consulting with Product and Engineering, case sensitive user names were implemented by design. At this point in time there are no plans to change this.
Case sensitive usernames adds a layer of security to credentials and login.
If you have a significant requirement for case in-sensitive usernames, the best way to do it would be for you to implement this on the client side or in Business Logic. A couple of options to do so are as follows.
1) When the user is created, implement Business Logic that automatically converts the username to lowercase.
2) In the client, you can convert the username to lowercase before sending it on login.
We hope that this helps. Please let us know if you have any questions.
Regards,
Billy Gee
X
Xavier De Leon
said
about 6 years ago
Appreciate the quick response. You might add to the documentation for the API that it's built that way be design as I found out only by accident and a developer might run in to the situation where an app ships and they are not aware it's case sensitive login.
Cheers.
B
Billy Gee
said
about 6 years ago
Hello Xavier,
That is an excellent suggestion. I will create an engineering escalation to recommend changes to our documentation regarding this toopic.
Xavier De Leon
On the iOS SDK it appears that the user name is case sensitive and it should not be. I checked the forums and there was an entry here titled "I think User Discovery should not be case sensitive" (https://support.kinvey.com/support/discussions/topics/5000040933) which has made 3 years ago and there's a comment about making it a feature request, but it appears that feature request has never been implemented.
The log in username should not be case sensitive. For example. if I create an account with a user name of "username@gmail.com" but then try to log in as "UserName@gmail.com" the login will fail because it's doing a case sensitive check of the user name and it should not.
Currently I work around this issue by converting the username to all lowercase when the account is created and when the user tries to log in. Also note that in my situation I use the email address as the username, but I store the email address and username separately. Regardless, user names should never be case sensitive. Only passwords should be case sensitive.
Hello Xavier,
As Pranav has mentioned, after consulting with Product and Engineering, case sensitive user names were implemented by design. At this point in time there are no plans to change this.
Case sensitive usernames adds a layer of security to credentials and login.
If you have a significant requirement for case in-sensitive usernames, the best way to do it would be for you to implement this on the client side or in Business Logic. A couple of options to do so are as follows.
1) When the user is created, implement Business Logic that automatically converts the username to lowercase.
2) In the client, you can convert the username to lowercase before sending it on login.
We hope that this helps. Please let us know if you have any questions.
Regards,
Billy Gee
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstPranav J
Xavier,
We are case sensitive by design but I will discuss this scenario with the backend team and get back to you with more information.
Thanks,
Pranav
Kinvey
Billy Gee
Hello Xavier,
As Pranav has mentioned, after consulting with Product and Engineering, case sensitive user names were implemented by design. At this point in time there are no plans to change this.
Case sensitive usernames adds a layer of security to credentials and login.
If you have a significant requirement for case in-sensitive usernames, the best way to do it would be for you to implement this on the client side or in Business Logic. A couple of options to do so are as follows.
1) When the user is created, implement Business Logic that automatically converts the username to lowercase.
2) In the client, you can convert the username to lowercase before sending it on login.
We hope that this helps. Please let us know if you have any questions.
Regards,
Billy Gee
Xavier De Leon
Appreciate the quick response. You might add to the documentation for the API that it's built that way be design as I found out only by accident and a developer might run in to the situation where an app ships and they are not aware it's case sensitive login.
Cheers.
Billy Gee
Hello Xavier,
That is an excellent suggestion. I will create an engineering escalation to recommend changes to our documentation regarding this toopic.
Regards,
Billy Gee
-
Why do I get "Undefined symbols" errors when building with KinveyKit?
-
How do I register push tokens?
-
When using social login, to perform a log-out, do I need to log out of the social network, Kinvey, o
-
How can I assign additional properties to users?
-
Does KinveyKit support 64-bit ARM devices, such as iPhone 5s?
-
Authorization Token Invalid or Expired
-
BOOL and how it is stored in the database.
-
Offline saving throwing errors
-
Custom endpoint not able to form request object
-
Security through business logic
See all 437 topics