Enable/DIsable Account API issue

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

Hi Team,

I’m trying to hit the Enable/DIsable account APIs but recieving error.

Below is my curl.

curl --location 'https://{mycompany}.api.identitynow.com/v3/accounts/a05630s0b5bfb422aa95cc56b32c8b9d/enable' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
  "externalVerificationId": "3f9180835d2e5168015d32f890ca1581",
  "forceProvisioning": true
}'

Getting this Response:

{
    "detailCode": "500.0 Internal fault",
    "trackingId": "ea80385dbd8f416aad91f3443bfb0be0",
    "messages": [
        {
            "locale": "en-US",
            "localeOrigin": "DEFAULT",
            "text": "An internal fault occurred."
        },
        {
            "locale": "und",
            "localeOrigin": "REQUEST",
            "text": "An internal fault occurred."
        }
    ],
    "causes": []
}

Appreciate any insights.

2

Hi,

Can you try from tenant once? I think there is an issue going on with enable and disable.

When I tried to disable account in sandbox tenant I got below.

image
image595×305 5.09 KB

-Abhinov

3

Hi,

Getting the same issue when I do it through UI in Sandbox.

image
image553×292 12.6 KB

Thanks.

4

Hi,

Yes, I think there is some issue internally.

Lets try after some time.

-Abhinov

1 Like
5

Hey,

Looks like issue solved now.

Can you try API now?

-Abhinov

6

Hey Abhinov, I am getting the same error as above. Was there a solution to this?

7

Hi,

I think this is from sailpoint side only and it resolved. What issue you are facing exactly?

-Abhinov

8

I’m getting the error message below when I try disable user via API.

{
“detailCode”: “500.0 Internal fault”,
“trackingId”: “17f2b4db950e4559832d5e10ab85f686”,
“messages”: [
{
“locale”: “en-US”,
“localeOrigin”: “DEFAULT”,
“text”: “An internal fault occurred.”
},
{
“locale”: “en-US”,
“localeOrigin”: “REQUEST”,
“text”: “An internal fault occurred.”
}
],
“causes”:
}

9

Hello,

I’m still having this issue above, is this an issue on my end?

10

I was not having issue when I was disabling bulk account via python script. It was working fine. Maybe your configuration/code have some issues internally?

11

I’m also having an issue and am researching now before i open a case. I think this is a bug. I can submit a request to disable an account via the api and get a 202 accepted and the task id returned to my script. in SailPoint Account Activity the request is there but as a Failure. So the API request does go through but something on the sailpoint end is failing. Disabling accounts in UI does work.

image
image1172×497 19.9 KB

12

LITERALLY JUST FIGURED IT OUT AFTER POSTING THE ABOVE!!!
So, using the documentation as my guide and what I can submit via postman, i was sending the request with a body like the documents show with externalVerificationId and forceProvisioning. I tried with various values as it says “if set” in the documenation for each so I sent empty strings for the first and all kinds of iterations of each. Turns out you do need the body but don’t need any content. So i just tried with an empty body and it worked.
I’m using powershell so my body was:

$body = @"
{
}
"@

I hope this helps others! I was up late last night trying so many things and fixed it in 5 minutes this morning!