SDK Case Sensitivity Skip to main content
https://support.okta.com/help/answers?id=906f0000000i00miac&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
Extranet AdminExtranet Admin 

SDK Case Sensitivity

I recently build a back-end admin app using Okta's .NET SDK.  One of the end-users noticed that the username value had to be entered in the same case as what's stored in the system.

This behavior is different from the Okta login form.  Also, the REST API does not perform a case sensitive comparison.

Considering that most Okta usernames are email addresses, can we assume that case-insensitive comparisons will always be supported?  If so, the "getByUsername( )" method in the .NET SDK should be fixed.

User-added image
Jaypee ManansalaJaypee Manansala (Okta)
Hi Jung,

Thanks for posting your inquiry in Okta Community.

Definitely you have a point here. I will send REQ ticket to Engineering Department on this behaviour.

Please let me know if you need any additional information. Thank you.

Best,

JP
Robert ZisonRobert Zison
Is there any news about this issue? I am using the same function and this is affecting me as well. Thanks!
Robert ZisonRobert Zison
You can get around this (I believe) by using a Linq query against the return value of GetUsersClient():

var user = oktaClient.GetUsersClient().FirstOrDefault(x => string.Equals(x.Profile.Login, username, StringComparison.CurrentCultureIgnoreCase));