PATCH- Update Account API

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi !
I have to use update-account | SailPoint Developer Community this API for one of the use case for reassigning the account. This API is throwing 404 but when I see in backend, then the account is getting reassigned to another identity. ( This 404 error is breaking my workflow.) Let me know your thoughts on this.

RequestBody-

[
  {
    "op": "replace",
    "path": "/identityId",
    "value":"************************************"
  }
]
2

Hi @deepakarora - Does this happen on v2024 API that you’ve linked or also on v3 or Beta APIs?

3

I have checked with v3 as well then also I got the same error.

4

How do you get the new identityId that you use in the API body, is it in one of the workflow variables?

5

Yeah. I am stroring into one variable then passing in the API call. If you leave the workflow for a sec, getting same error through postman as well.

6

Can you try re-generating the OAuth credentials, setting the scope to “all” and see if you still get the same error? If you don’t get the error, reduce the scope back to what you’ll require for the workflow.

7

I am already using scope:all for this.

8

Do you get the same 404 even if you hardcode the new identityId (just to test the API)? If so there might be something else going wrong. It’s strange how the reassignment goes through but you get a 404.

1 Like
9

Initially when I got error in workflow then first, I tested from postman only then I noticed this strange behavior.

10

Hi @deepakarora,

I tried the operation and found that if you enter incorrect IDENTITY ID in request body, you get 400 Bad Request. Only in case of incorrect Account ID in the params you get 404.

I am pretty sure you checked this part but still if you could have a look at the account ID in the params and make sure that is correct just to be double sure.

You could check this directly in postman as well.

11

Deepak follow the examples on the BETA api

Screenshot 2024-10-03 084658
Screenshot 2024-10-03 0846581002Ă—585 29.7 KB

1 Like
12

Hi Tom!
There is no issue in replacing the attribute value even using v3 and v2024. I am replacing the identityId and reassigning the account to the identityId.

13

@deepakarora It should have the same response

"op": "replace",
"path": "/identityId",
"value": "2c9180857725c14301772a93bb77242d"
14

Yes. It should but not behaving same.

image
image1346Ă—932 47.6 KB

15

@deepakarora it cant find the ID you want to replace it with

16

Hi! Everything is correct. Even it’s reassigning the account to the identityId in the backend (strange behaviour) but API is throwing 404 so it’s breaking my workflow.

17

@deepakarora check your Headers