Forum Discussion
MicrosoftAzure AD SCIM Validator is in General Availability (GA) Status
Can the SCIM Validator be made open source or at least have a location where issues can be filed against it? We've encountered a couple problems with the SCIM Validator and would like some way of reporting issues or discussing misunderstandings with the developers.
The first is that it does not read the schema correctly. For instance, our endpoint describes the 'email' 'primary' attribute as boolean, but SCIM Validator sets it to string, apparently ignoring our schema.
Another is a failure during group testing where it re-creates a user that already exists. It seems not to expect a 409 reply.
It is very hard to tell *what* the tester expects without a diagnostic error or insight into its source code.
Vincent_Drake_Cerberus I'm so glad I'm not alone, and want you to know that you're not alone either! I've spent the past few days trying to figure out what I'm doing wrong. I finally reached the same conclusion that the validator doesn't expect a 409 to be returned after looking through my server logs.
The validator makes a patch request to change a username from 'x' to 'y' as part of a completely different test, and then as part of the failing test, the first thing it tries to do is submit a post request for a user with username 'y'... I can get it to pass by removing the duplicate user throws an error code (and just returning the user instead), but then the Create a duplicate User test obviously fails.
Very strange that the otherwise randomly generated test data is kept between tests.
- I'm also seeing the 409 for 'Patch Group - Remove Member'
I'm also having trouble getting 'Patch Group - Replace Attributes' to work. It looks like it's trying to make a group a member of another group, which is not something we support. We've adjusted the schema to say we only support users as members of a group but that doesn't seem to help
- "Can the SCIM Validator be made open source or at least have a location where issues can be filed against it?"
Did anything like this happen? I'm searching around for any docs / issue tracker and not coming up with anything.
I am also having issues understanding the errors I'm being shown:
1. When I look at the "Show Details" for any of my failed requests they are all showing as POST requests, even though I'm 90% certain they are using other HTTP verbs (DELETE, PATCH, PUT)
2. When I look at the url under "Show Details" it appears to always be the top level URL that I entered into the test field, not the specific URL hit by the test (eg: Update group membership does not show what is used as the id for the path parameter to identify the group) 
owinoakeloVincent_Drake_Cerberus We released a fix that addresses the read schema issues. The new release also addressed the duplicate creation the triggers the 409 error.
To the question on having the making the validator open source, we do not have that in the current plan. We are working on a channel to enable you raise issues.
