Q: Is Azure wrong about removing group members?

[nlfiedler]

I would post this as a discussion as this is not so much a bug as a question.

The question is this: is Azure removing group members incorrectly? They send this:

{
    'schemas': ['urn:ietf:params:scim:api:messages:2.0:PatchOp'],
    'Operations': [{
      'op': 'Remove',
      'path': 'members',
      'value': [{ 'value': 'user-joe' }]
    }]
}

Not surprisingly, this has no effect when passed to scim-patch, since according to 3.5.2.2 this format is not one of the mentioned possibilities. It seems perfectly reasonable to expect the remove operation to look like the add operation as described in 3.5.2.1, so I can sympathize with their wishful thinking.

The fun part now will be fixing their requests since I have no control over what they send or what the standard specifies.

Also filing this so other people can find this and not spend too much time trying to debug the issue.

[ZeRego]

I would like to see the library support this behaviour as well. This would be introduced behind a config flag to keep it backwards compatible.

const patchedUser = scimPatch(scimUser, patch, {allowRemoveByValue: true})

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.