Possible non-compliance in Postman tests

[roadSurfer]

Apologies if this is not the correct place to raise this.
I have noticed what I think are some minor issues with the Postman tests:

1. Casing - JSON is case sensitive and some of the attributes are incorrectly cased (e.g. "UserName"). (This can worked gotten around server-side, e.g. by telling Jackson to operate in a case insensitive manner).
   Are the Postman tests and accurate reflection of how Azure AD interacts and I should prepare to deal with variance from spec, or are these simple oversights and easily corrected?
   Thanks.

[ArvindHarinder1]

Thanks for reporting. We'll take a look and get back to you.

[ArvindHarinder1]

this was a mistake, feel free to create a PR to change the test. https://github.com/AzureAD/SCIMReferenceCode/blob/master/PostmanCollection.json

[roadSurfer]

Thanks, I have already forked it on Postman and updated a few parts to bring it closer to what Azure AD is sending. Once I have confidence my changes are accurate, I can fork again in GitHub and apply the changes.

[nathan-c]

Given the SCIM spec asks for case insensitive attributes it is probably good to have some tests to cover this https://tools.ietf.org/html/rfc7643#section-2.1