Identity Security Cloud Governance - Bad Client Credentials

Identity Security Cloud (ISC) ISC Discussion and Questions
1

We are receiving “Bad Client Credentials” when trying to use a PAT as denoted in the documentation.

We get further if we use API Key generation and generate client credentials. But in this scenario, entitlements can be aggregated, but accounts cannot.

When trying to aggregate accounts (only), we receive the following.

[ConnectorError] 403 [Possible Suggestion] Ensure that configuration parameters is correct and service account is having required permissions. ERR_BAD_REQUEST, Request failed with status code 403, {“detailCode”:“403 Forbidden”,“trackingId”:“fdc94b8af0f6442db5f8fe0f7d2b4ad8”,“messages”:[{“locale”:“en-US”,“localeOrigin”:“DEFAULT”,“text”:“The server understood the request but refuses to authorize it.”},{“locale”:“und”,“localeOrigin”:“REQUEST”,“text”:“The server understood the request but refuses to authorize it.”}],“causes”:} (

2

Hi Robert,

Thank you for your input. This appears to be related to using the product features. I’ve moved your comment to our ISC Discussions and Questions category for greater help from the community.

3

We determined that because we were using network whitelisting, the networks where SailPoint resides had to be added to our trusted networks.

1 Like