Skip to content

Conversation

kalenjohnson
Copy link

This covers the enterprise options when a value needs to be added or replaced. The current implementation will only search urn:ietf:params:scim:schemas:core:2.0:User when the value may be in urn:ietf:params:scim:schemas:extension:enterprise:2.0:User

This covers the enterprise options when a value needs to be added or replaced
@kalenjohnson
Copy link
Author

kalenjohnson commented Jun 26, 2025

I am new to SCIM provisioning in general, however this will correct patch requests to enterprise user schema values

image

Request:

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:PatchOp"
  ],
  "Operations": [
    {
      "op": "replace",
      "path": "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber",
      "value": "65489745"
    }
  ]
}

Response:

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "detail": "Unknown path: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber, in object: urn:ietf:params:scim:schemas:core:2.0:User",
  "status": 404
}

@arietimmerman
Copy link
Collaborator

arietimmerman commented Aug 23, 2025

Thanks for reporting.
I created a slightly different solution to ensure you change the intended attribute. Nevertheless, thanks for reporting and the idea on how to fix it. See #120
See it in action here: https://scim.dev/playground/users.html#update-extension-attribute

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants