Anggakara
Anggakara•7d ago

SCIM Update and Delete

hey team, thank you for your hardwork. is zitadel already support these update and delete scim endpoint? - https://scim.dev/playground/users.html#update-attribute - https://scim.dev/playground/users.html#delete whenever we make changes it keep returning this error 
Error code
SystemForCrossDomainIdentityManagementServiceIncompatible
Error message
StatusCode: BadRequest Message: Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details. Web Response: {"schemas":["urn:ietf:params:scim:api:messages:2.0:Error","urn:ietf:params:scim:api:zitadel:messages:2.0:ErrorDetail"],"scimType":"invalidPath","detail":"Failed to evaluate path","status":"400","urn:ietf:params:scim:api:zitadel:messages:2.0:ErrorDetail":{"id":"SCIM-opzz8","message":"Failed to evaluate path"}} . This operation was retried 1 times. It will be retried again after this date: 2025-11-03T14:16:43.6606724Z UTC
Error code
SystemForCrossDomainIdentityManagementServiceIncompatible
Error message
StatusCode: BadRequest Message: Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details. Web Response: {"schemas":["urn:ietf:params:scim:api:messages:2.0:Error","urn:ietf:params:scim:api:zitadel:messages:2.0:ErrorDetail"],"scimType":"invalidPath","detail":"Failed to evaluate path","status":"400","urn:ietf:params:scim:api:zitadel:messages:2.0:ErrorDetail":{"id":"SCIM-opzz8","message":"Failed to evaluate path"}} . This operation was retried 1 times. It will be retried again after this date: 2025-11-03T14:16:43.6606724Z UTC
i know you guys already mention in your docs that the scim groups still not supoorted yet until next feature, but is this basic user scim endpoint also not supported yet? please guide me ya, in case i miss something
Users | scim.dev
Learn about SCIM Users, entities with access to a system or application. Understand how to manage these users across various systems using SCIM's standardized methods. Discover how to list, find, and filter users through a RESTful API.
1 Reply
Ask Inkeep
Ask Inkeep•7d ago
Hi @Anggakara, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question. Answer Yes, ZITADEL supports both PATCH (update) and DELETE operations for SCIM users (1) . According to the SCIM v2.0 documentation, the following endpoints are supported: - PATCH /scim/v2/{orgId}/Users/{id} for modifying a user - DELETE /scim/v2/{orgId}/Users/{id} for deleting a user The error you're receiving ("scimType":"invalidPath","detail":"Failed to evaluate path") suggests an issue with how the path is being specified in your PATCH request (2) . Here are working examples from the documentation: PATCH example - Set a user inactive: 
curl -X PATCH "<https://$%7BDOMAIN%7D/scim/v2/$%7BORG_ID%7D/Users/$%7BUSER_ID%7D%22> \
 -H 'Content-Type: application/scim+json' \
 -H 'Accept: application/scim+json' \
 -H "Authorization: Bearer ${ACCESS_TOKEN}" \
 --data-raw '
 {
 "schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
 "Operations": [
 {
 "op": "replace",
 "path": "active",
 "value": false
 }
 ]
 }
 '
curl -X PATCH "<https://$%7BDOMAIN%7D/scim/v2/$%7BORG_ID%7D/Users/$%7BUSER_ID%7D%22> \
 -H 'Content-Type: application/scim+json' \
 -H 'Accept: application/scim+json' \
 -H "Authorization: Bearer ${ACCESS_TOKEN}" \
 --data-raw '
 {
 "schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
 "Operations": [
 {
 "op": "replace",
 "path": "active",
 "value": false
 }
 ]
 }
 '
DELETE example: 
curl -X DELETE "<https://$%7BDOMAIN%7D/scim/v2/$%7BORG_ID%7D/Users/$%7BUSER_ID%7D%22> \
 -H "Authorization: Bearer ${ACCESS_TOKEN}"
curl -X DELETE "<https://$%7BDOMAIN%7D/scim/v2/$%7BORG_ID%7D/Users/$%7BUSER_ID%7D%22> \
 -H "Authorization: Bearer ${ACCESS_TOKEN}"
The key is ensuring your PATCH request follows the correct format with the schemas array containing "urn:ietf:params:scim:api:messages:2.0:PatchOp" and properly structured Operations array . If you're still experiencing issues, could you share the exact PATCH request body you're sending? That would help identify the specific path evaluation problem. ​ To learn more, see the sources I considered: [1] SCIM v2.0 (Preview) [2] SCIM v2.0 (Preview) ​ Feel free to tag @Ask Inkeep with additional questions.

Did you find this page helpful?