Forum Discussion
owinoakelo
Microsoft
MicrosoftAzure AD SCIM Validator is in General Availability (GA) Status
You can now validate the compatibility of your SCIM provisioning endpoint and Azure AD code base using our Azure AD SCIM Validator. This tool can be used by ISVs who want to build SCIM compatible ser...
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.
"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)
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)
