You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All other user routes work because the target /Users (with a capital "U"); however the GET empty Users test in the Endpoint tests targets the /users route (lower case "u").
This is causing the test to fail for me because our application respects the case-sensitivity of the resource.
While the SCIM specification explains that the JSON attributes should be treated case-insensitively, it does not say anything explicitly about the case-sensitivity of the Resource route paths. The RFC only shows examples with /Users and /Groups (no mention of /users or /groups)
I'm curious if treating this route case-insensitively is a hard requirement for Azure AD SCIM applications or if this was a bug in the postman test.
The text was updated successfully, but these errors were encountered:
All other user routes work because the target
/Users
(with a capital "U"); however the GET empty Users test in the Endpoint tests targets the/users
route (lower case "u").This is causing the test to fail for me because our application respects the case-sensitivity of the resource.
While the SCIM specification explains that the JSON attributes should be treated case-insensitively, it does not say anything explicitly about the case-sensitivity of the
Resource
route paths. The RFC only shows examples with/Users
and/Groups
(no mention of/users
or/groups
)I'm curious if treating this route case-insensitively is a hard requirement for Azure AD SCIM applications or if this was a bug in the postman test.
The text was updated successfully, but these errors were encountered: