SCIM Modify Failing in SailPoint IIQ (PATCH 404 / PUT 405 Error)

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Hi Team,

I’m encountering an issue with SCIM-based update (modify) operations from SailPoint IdentityIQ (IIQ) and wanted to check if anyone has seen something similar.

All other operations are working as expected, but the modify operation is failing.

Issue Details

  • When usePatch = true is configured in the application XML, SailPoint sends a SCIM PatchOp (PATCH) request.

    The payload sent by SailPoint looks like this:

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

→ This results in a 404 Not Found error.

When usePatch = false (i.e., using PUT), the request fails with:

→ **405 Method Not Allowed

Working Scenario (Postman)**

The same API works correctly when tested via Postman using a PATCH request with the following payload:

{
"id": "....",
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"userName": "Testuser",
"name": {
"familyName": "Test",
"givenName": "User"
},
"displayName": "Test User1",
"active": true
}

Has anyone experienced a similar issue with SCIM modify operations in SailPoint IIQ? Any suggestions or insights would be greatly appreciated

2

@aniketnegi Could you please try adding below entry to app xml and test:

 entry key=“disableStrictParsing” value=“true”
3

Hi @neel193 Thanks for replying. I tried as you have suggested, but it failed with same 404 error.

4

@aniketnegi Did you enable the logs ? inspect what URL is being hit during modify. could you please share logs.

5

@aniketnegi Have you tried the scim call in Postman? Could you please share the request format?

6

The issue could be Target API doesn’t support SCIM PatchOp — it expects PATCH with a full resource body, not an Operations array. PUT is also not supported (405).

The easiest fix would be Set usePatch=false and configure a Before Rule on the Modify endpoint to override the verb to PATCH and inject a full resource body matching what the target accepts.

7

Now the operation shows successful after target app team restructured their payload. However, it does not change the sent data in target. It just shows success in admin console of IIQ.

Any suggestions please?

8

did you implement this one, which i suggested…

9

As I am using SCIM connector, using before rule I can only change the provisioningplan I believe. I am not sure if we can change the HTTP operation.

If it was Webservice, we can do it in before opeartion rule I believe.

Please let me how can we do it using SCIM connector, if it is possible.

10

Please find it below

{

  "schemas": [

    "urn:ietf:params:scim:api:messages:2.0:PatchOp"

  ],

  "Operations": [

    {

      "op": "replace",

      "path": "familyName",

      "value": "Updated-givenName"

    }

  ]

}

And I am passing in id ins parameters

11

Hello @narayanag - I am trying to get logs. Will share.