bdemers commented on issue #436: URL: https://github.com/apache/directory-scimple/issues/436#issuecomment-1850361386
Good find @kjthorpe18! I agree that does look out of spec: > If the target location is a multi-valued attribute and no filter is specified, the attribute and all values are removed, and the attribute SHALL be considered unassigned. There is no filter in that request. That said, I'm guessing this looks specific enough were we could support it out of the box: e.g. if a `remove` request is formatted like this, remove that value (possibly normalize the request, anything else processing this operation sees it as `"path":"members[value eq \"<value>\"]"` Worst case we can add some sort of flag (system property or something), `scimple.azure.workarounds=true` But I do think the intention of this patch operation is clear. Thoughts? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
