You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They sometimes send this operation when there isn't a multi-valued attribute of that type. When this happens, the scim-patch library applies the update in a way that introduces a circular reference to the resource object. This causes errors when we call JSON.stringify on the resource object.
Expected behavior
We would expect operations to be applied to resources in a way that doesn't introduce a circular reference in the object. Though, admittedly, this update is a bit strange from Azure AD SCIM (the value should be a string here I believe, and this only seems to happen with an empty object).
Additional context
We wanted to flag this in the upstream library. We're currently looking at workarounds on our end to either edit the resource before sending it to the library, or checking for circular references when we get the resource from the library.
The text was updated successfully, but these errors were encountered:
blairlunceford
changed the title
Specific replace op results in circular reference
Replace op with value of empty object results in circular reference
Sep 18, 2023
Describe the bug
We've seen Azure AD SCIM send replace operations with an empty object in the
value
field:They sometimes send this operation when there isn't a multi-valued attribute of that type. When this happens, the
scim-patch
library applies the update in a way that introduces a circular reference to the resource object. This causes errors when we callJSON.stringify
on the resource object.To Reproduce
Expected behavior
We would expect operations to be applied to resources in a way that doesn't introduce a circular reference in the object. Though, admittedly, this update is a bit strange from Azure AD SCIM (the value should be a string here I believe, and this only seems to happen with an empty object).
Additional context
We wanted to flag this in the upstream library. We're currently looking at workarounds on our end to either edit the resource before sending it to the library, or checking for circular references when we get the resource from the library.
The text was updated successfully, but these errors were encountered: