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...
We've got a very simple schema that only includes the following user attributes (All required) with no group support:
- • userName
- • active
- • emails[type eq "work"].value
- • name.givenName
- • name.familyName
When I run the validator I'm getting the following error: Unknown test failed. Object ref not set to an instance of an object
"FailedTests": [
{
"$id": "31",
"Description": "One or more errors occurred. (Object reference not set to an instance of an object.)",
"Name": "Unknown test failed",
"Results": [
{
"$id": "32",
"Message": "Internal server error: One or more errors occurred. (Object reference not set to an instance of an object.)",
"Outcome": 1,
"MoreInformation": ""
}
],
"ResponseHeaders": "",
"ResponseStatus": "One or more errors occurred. (Object reference not set to an instance of an object.)",
"ResponseBody": "",
"InitialRequestBody": "",
"RequestBody": "One or more errors occurred. (Object reference not set to an instance of an object.)",
"SFComplianceOptional": false,
"HasTestPassed": false,
"TestexecutionTime": 0
}
],
I've run through the postman tests directly and they're all passing, or failing for valid reasons i.e.
- Get User Filters fails due to DisplayName not being supported in our schema
- Get User1 Check Patch due to Formatted not being supported in our schema
- Create user1 fails as emailName357 is not a valid email address format
I can change the above 3 tests to use valid data and then they pass as expected
Based on the above, I'm not seeing anything wrong with our implementation. Is the error an issue with the scim validator itself or am I missing something? How do we proceed with getting our implementation approved?