Set IIQDisabled value via API For Delimited

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

Hello Everyone,

I want to set the IIQDisabled value as true for accounts via API for a delimited source. I am trying both PATCH as well as PUT Accounts api, but none seems to be working.
For PATCH, I am using the below body:
[
{
“op”: “replace”,
“path”: “/attributes/IIQDisabled”,
“value”: true
}
]

Error: Invalid “path”: “/attributes/IIQDisabled” of JSONPatch: {
“op”: “replace”,
“path”: “/attributes/IIQDisabled”,
“value”: true
}

For PUT, I am using the below body:
{
“attributes”: {
“btEIN”: “MUITA007”,
“IIQDisabled”: true,
“UserAccess”: “Global Disablement Group”,
“givenName”: “MUITA007”,
“familyname”: “srivastava”,
“e-mail”: “[email protected]”
}
}

Error: 400 Bad Request- “The request was syntactically correct but its content is semantically invalid.”

What exactly am I doing wrong here?

2

I tried in my postman. It is working
Can you check in headers if you are passing correct Content-Type in your patch call. I used below
image

3

Hi @sandashafreen26

my account schema of Delimited Source

image
image957×238 4.82 KB

my source file

image

UI:

image
image836×163 7.57 KB

account details page:

image
image921×502 17.5 KB

JSON:

image

{
"attributes": {
            "IIQDisabled": "false",
            "acctid": "123",
            "acctname": "reddy"
            }
}

image
image850×167 8 KB

account details page:
image
image915×516 18.6 KB

4

Similarly, the patch also working fine:

image

[
  {
    "op": "replace",
    "path": "/attributes/IIQDisabled",
    "value": "true"
  }
]

do let me know if you need any more details.

5

Hi @sandashafreen26

Just make sure you have the correct double quotes; I observe the difference in double quote character like " vs “

correct double quote character

[
{
"op": "replace",
"path": "/attributes/IIQDisabled",
"value": true
}
]

wrong double quote character

[
  {
    “op“: “replace“,
    “path“: “/attributes/IIQDisabled“,
    “value“: true
  }
]

if above is not the case, then cross check the following.

  1. Your environment variables
  2. the JSON body if any hidden characters, open in code editor (like VS Code or Notepad++)
  3. Cross check the correct id of the account mentioned in Params
    {this ID value copy from account details page}
    image
    image798×281 15.8 KB
6

Thanks for your response.
I tried the same PATCH body to disable the account on a different source and it worked. But somehow it is not working on a particular source. The only difference between the two sources is that the accounts were created via create account API on which this PATCH api isn’t working.

1 Like