Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postman GET empty Users in Endpoint tests having issues #43

Open
rdelao opened this issue Oct 27, 2020 · 0 comments
Open

Postman GET empty Users in Endpoint tests having issues #43

rdelao opened this issue Oct 27, 2020 · 0 comments
Labels
question Further information is requested test Issue with a test

Comments

@rdelao
Copy link

rdelao commented Oct 27, 2020

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.

@marcusca10 marcusca10 added question Further information is requested test Issue with a test labels Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested test Issue with a test
Projects
None yet
Development

No branches or pull requests

2 participants