Scim connector Patch error on path parameter

Hi, I’m having an issue with a SCIM Core v2 connector. I’m integrating a target system that has PATCH enabled for updates, but for some fields it accepts the integration without the path attribute, while for others it strictly requires it. Is there a way to configure this behavior in One Identity?

I’m attaching what the connector sent and what the target requires:


"schemas": [
"urn:ietf:params:scim:api:messages:2.0:PatchOp"
],
"Operations": [
{
"op": "replace",
"value": {
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
"department": "TestBU",
"taxonomies": [
{
"displayName": "Group B",
"type": null
}
]
}
}
}
]
}"

Requested from target:

        {            "op": "Replace",   

         "path": "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter",   

         "value": "VALUE"        }

Parents Reply
  • Hi Tino,

    thanks for your quick reply Grinning

    Changing the target product did not change the JSON payload produced by the connector and thus didn't solve the problem.

    What I found out (tested using Postman):

    This is the payload produced by the OIM connector which leads to the problem:

      "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:PatchOp"
      ],
      "Operations": [
        {
          "op": "replace",
          "value": {
            "displayName": "Test Anton"
          }
        }
      ]
    }

    If you change it slightly, using "path", Meshcloud accepts it:

    {
      "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:PatchOp"
      ],
      "Operations": [
        {
          "op": "replace",
          "path": "displayName",
          "value": "Test Anton"
          }
      ]
    }

    Seems Meshcloud supports "path" as described in https://www.rfc-editor.org/rfc/rfc7644#section-3.5.2,

    but does not support "replace" as described in https://www.rfc-editor.org/rfc/rfc7644#section-3.5.2.3.

    Is there a way to change the behavior of the OIM connector?

Children