Scim Validator Issues with Groups Display Name

Question

Scim Validator Issues with Groups Display Name

Mitchell Mecca 0

Correlation ID: 5f7d86bd-0c66-42c5-abc3-943dd27d4ab5

Timestamp (UTC): 2025-11-14T21:44:16.008Z The error explains the the displayName should have change but looking at the details shows that it did change. User's image

User's image

I also had a similar issue with a custom extension with the type Array of String which when away when I switched to String. That one is probably do to not using the correct comparison operation on the array.

VEMULA SRISAI 13,990 Reputation points Microsoft External Staff Moderator

2025-11-18T06:18:39.56+00:00

Hello Mitchell Mecca ,

Thank you for the information. Based on the SCIM Validator output, the error is triggered because the validator detects a mismatch in the expected vs. returned value for the displayName attribute. Although the value appears to have changed, this usually happens when the SCIM service is not returning the attribute in the exact format or data type defined in the schema.

Since you previously observed a similar issue with an attribute defined as an Array of String, this is likely related to the comparison logic on the SCIM provider side (for example, returning an array instead of a string, or returning the value in an unexpected structure).

To move forward, please verify the following on your SCIM implementation:

displayName is returned strictly as a string, not as an array or nested object.

The PATCH response returns the updated resource correctly, or a valid 204 response with no body.

Attribute formatting and types match the SCIM schema definitions exactly.

If possible, please provide the full SCIM request and response payloads so we can review the attribute structure and identify the exact mismatch.

Your answer

VEMULA SRISAI 13,990 Reputation points Microsoft External Staff Moderator

2025-11-18T06:18:39.56+00:00

Hello Mitchell Mecca ,

Thank you for the information. Based on the SCIM Validator output, the error is triggered because the validator detects a mismatch in the expected vs. returned value for the displayName attribute. Although the value appears to have changed, this usually happens when the SCIM service is not returning the attribute in the exact format or data type defined in the schema.

Since you previously observed a similar issue with an attribute defined as an Array of String, this is likely related to the comparison logic on the SCIM provider side (for example, returning an array instead of a string, or returning the value in an unexpected structure).

To move forward, please verify the following on your SCIM implementation:

displayName is returned strictly as a string, not as an array or nested object.

The PATCH response returns the updated resource correctly, or a valid 204 response with no body.

Attribute formatting and types match the SCIM schema definitions exactly.

If possible, please provide the full SCIM request and response payloads so we can review the attribute structure and identify the exact mismatch.