[SCIM] PATCH `Add` operation on already exists resource
See original GitHub issueIf an already exists member is re-added an 409 error response with duplicate reference error is returned. According to the Add Operation RFC:
 
Input example:
{
  schemas: ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
  Operations: [{
    op: "add",
    path:"members",
    value: [{
      value: ...,
      display: ...
    }]
  }]
}
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
 Top Results From Across the Web
Top Results From Across the Web
SCIM Group Patch add member returns 500 for existing ...
However, when we add a member to a group, who already exists on the particular group, it turns out 500 internal server error....
Read more >Can PUT create a resource which does not exist?
I am trying to implement a SCIM REST API and got a small confusion with respect to PUT operation. As per SCIM RFC...
Read more >Known issues and resolutions with SCIM 2.0 protocol ...
This article describes current and past issues with the Azure AD user provisioning service's adherence to the SCIM 2.0 protocol, and how to...
Read more >SCIM 2.0 Protocol Reference
The User creation operation brings the user's application profile from Okta ... Okta checks that the User object exists on the SCIM server...
Read more >SCIM 2.0 PATCH Operations - PingDirectoryProxy
When using a PATCH request to modify a SCIM 2.0 resource that has one or more required SCIM 2.0 attributes, the requester must...
Read more > Top Related Medium Post
Top Related Medium Post
No results found
 Top Related StackOverflow Question
Top Related StackOverflow Question
No results found
 Troubleshoot Live Code
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free Top Related Reddit Thread
Top Related Reddit Thread
No results found
 Top Related Hackernoon Post
Top Related Hackernoon Post
No results found
 Top Related Tweet
Top Related Tweet
No results found
 Top Related Dev.to Post
Top Related Dev.to Post
No results found
 Top Related Hashnode Post
Top Related Hashnode Post
No results found

Some changes have been made in the branch “release/2.0.6”:
Hello,
First thank you for your feedback. Indeed, the condition must be updated otherwise unexpected conditions can occurred. We are going to update the branch “release/2.0.6” to fix this issue.
Kind Regards,
SimpleIdServer