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...
owinoakeloSchema Discovery does not seem to work for us, the SCIM validator then fails to execute any tests. However, it does work when using the Default schema option.
Our endpoint supports the following attributes: userName, externalId, active, displayName, emails, roles. If I select Default schema and manually edit the attribute mappings, the SCIM Validator succesfully validates the SCIM endpoint implementation in our application. All 10 tests are completed succesfully.
If I select Schema Discovery, the SCIM validator successfully fetches the attribute definitions from our /Schemas endpoint. However, if I then click Test Schema, the validator always returns an error message: SCIM Validation failed. NetworkError when attempting to fetch resource.
The browser console log shows some CORS errors. I do not see any incoming requests in our application.
Why would Test Schema fail to contact our endpoint when using Schema Discovery?
owinoakeloMicrosoft
MicrosoftWMRutten , yes we are experiencing a network issue with some endpoints thus the CORS issue. There is an active work to fix it. I recommend you use the default schema or upload schema options as we work on fixing the issue affecting schema discovery.