ISC: 500.2.1 Data integrity issue

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

Dear ISC Community,

While calling the API {{baseUrl}}/accounts/:id/entitlements we get the following 500 Internal Server Error for multiple accounts:

{
    "messages": [
        {
            "localeOrigin": "DEFAULT",
            "text": "Persistent data is in a bad state.",
            "locale": "en-US"
        },
        {
            "localeOrigin": "REQUEST",
            "text": "Persistent data is in a bad state.",
            "locale": "en-US"
        }
    ],
    "detailCode": "500.2.1 Data integrity issue",
    "trackingId": "68ab00f9d09d4b308ae6882450149faf"
}

The error is visible in the UI as well (as the same API is used).

Did you encounter this issue until now?
Do you know if SailPoint monitors such errors and proactively works to resolve them?

Best regards,
Andrei

2 Likes
2

hi Andrei, just started seeing this after updating account query on a JDBC connection. Have you had any luck with your issue?

Thanks,
Deepika

3

Hi @adamian / @deepika_reddy2 ,

Can you try below curl to get account entitlements it is working find below screenshot for your reference:

image
image905×395 27 KB

curl --location -g --request GET ‘https://{tenant}.api.identitynow-demo.com//v3/accounts/:id/entitlements’
–header ‘Accept: application/json’
–header ‘Authorization: Bearer {{token}}’

Thank You.

4

Hi @gogubapu, we already see the error for different accounts (not all) using Postman and the ISC UI, it makes no sense to expect something different by using curl.

Hi @deepika_reddy2, a ticket is open with SailPoint. I wonder how much time they will need to debug this issue (which happens on their side), as they kept asking for similar information.

Later edit, 13.11.2024, as I can’t post any replies.

SailPoint support informed us that

Thanks for the patience, we’ve been working with the engineering team on this concern and we’ve deployed some changes in production.

The API doesn’t return an error anymore.

On the other side, it seems that the data returned is incomplete/incorrect, as the AD entitlement is missing some attributes (name, attributes object, description).
This is visible in the API returned object and in the UI.

The same AD group is correctly displayed in another source (the Admin accounts source), so my assumption is that the data got corrupted in the cloud. To fix the issue, they just ignore the corrupted data and returned other available data.
The entitlements aggregation runs daily, but it seems that it does not overwrite the corrupted data.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.