Service Desk Integration http request method change to PUT

Hi,

I need to change the default HTTP method in the generic servicedesk intgeration to PUT and not POST as the ticket system we are going to integrate with requires the method to be PUT.

I have tried the following in the JSON config of the service desk connector with no luck:

“httpMethodType”: “GET”,

“htttRequestMethod”: “GET”,

But the result do not influense the request being sent:

POST /entity/Default/24.200.001/Case HTTP/1.1
Authorization: Bearer JwQ812XM2B731Ktab9GPn-Mcdvp3_r1FyiE1yjzTSUQ
Accept: application/json
Content-Type: application/json
Content-Length: 158
Host: 192.168.66.31:8888
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.5.13 (Java/17.0.19)
Accept-Encoding: gzip,deflate

{“ClassID”:{“value”:“JREPAIR”},“BusinessAccount”:{“value”:“ASEC”},“ContactID”:{“value”:“NIco Prinsloo”},“Subject”:{“value”:“Juicer repair - not powering on”}}

Is it possible to change this.

Thanks

Hello Nico,

I don’t think this is configurable directly in the Generic SDIM connector.

The PUT you see in SailPoint’s Service Desk Integration API is for updating the SDIM configuration itself, not for changing the outbound ticket creation call that SDIM sends to the ITSM system.

For ticket creation, Generic SDIM lets us configure the resource endpoint, payload fields, request root element, response element, and custom headers, but I don’t see a supported property for changing the HTTP method from POST to PUT. So adding fields like httpMethodType or htttRequestMethod will may be just ignored because they are not part of the supported ticket creation config.

If the target system only accepts PUT, the practical options would be:

  1. Put a small middleware/proxy in between. SailPoint sends the normal SDIM POST to the middleware, and the middleware forwards it as PUT to your ticketing API.
  2. Use an ISC Workflow HTTP Request action instead, since workflow HTTP Request supports PUT, but then you lose the normal SDIM fulfillment flow unless you build that handling around it.

For pure Generic SDIM ticket creation, I would treat POST as fixed unless SailPoint confirms an internal/custom option through Support.

Hi @scorpionza

We had a similar use case but for a different SDIM tool. We used the Workflow way to call the API with their respective methods.

Also, as @punna0001 mentioned Using this approach, you will lose the normal SDIM fulfillment flow.