Currently, when removing an email in the patch request, if the value in the remove operation not match the current value, the value in the remove operation will be set the user.
e.g. Current User
{..., "emails": [["type": "work", "primary": true, "value": "original@example.org"]]}, ...}
After Apply Patch {"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations":[{"op":"Remove","path":"emails[type eq \"work\"].value","value":"updated@example.org"}]}
The user will be updated to {..., "emails": [["type": "work", "primary": true, "value": "updated@example.org"]]}, ...}
Currently, when removing an email in the patch request, if the value in the remove operation not match the current value, the value in the remove operation will be set the user.
e.g. Current User
{..., "emails": [["type": "work", "primary": true, "value": "original@example.org"]]}, ...}
After Apply Patch
{"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations":[{"op":"Remove","path":"emails[type eq \"work\"].value","value":"updated@example.org"}]}
The user will be updated to
{..., "emails": [["type": "work", "primary": true, "value": "updated@example.org"]]}, ...}