Follow on to this thread:
One of the SCIM CRUD API tests here is failing for my SCIM integration: Test your Okta SCIM integration | Okta Developer
The test creates a user with an uppercase email and then asserts that when you GET the information for the user over my SCIM api, the “emails” field in the User schema matches exactly.
My application stores all its emails case insensitively in lowercase in our database, so the test fails because we return the emails in lowercase instead of in a mixture of uppercase and lower…
Similar to this thread I was testing my SCIM API using the Runscope testing instructions and failing since our db stores the username in lowercase. According to the SCIM spec this is valid since the username is case insensitive.
Could the test script to be updated with case insensitivity in mind? This would better match the expected behavior, and reduce false alarms for other devs using these testing tools in the future.
It looks like there hasn’t been an updated response since May of 2023. Just wanted to get confirmation that this is still valid.
As @andrea mentioned, it’s all right if your SCIM server is not case sensitive when it comes to usernames, just make sure to leave a note on your submission.
system
November 22, 2024, 10:27am
3
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.