What problem are you observing?
When calling the v2024/access-profiles/:id endpoint on our staging enviorment, the service returns a 500 server error:
Exception: Response status code does not indicate success: 500 (). | {"messages":[{"localeOrigin":"DEFAULT","locale":"en-US","text":"An internal fault occurred."},{"localeOrigin":"REQUEST","locale":"en-US","text":"An internal fault occurred."}],"detailCode":"500.0 Internal fault","trackingId":"c6d09c3a117f46a68c496b22650b089c"}
This is the type of body we are sending to the endpoint:
[
{
"op": "replace",
"path": "/entitlements",
"value": [
{
"id": "2c9180857725c14301772a93bb77242d",
"type": "ENTITLEMENT",
"name": "AD User Group"
}
]
}
]
What is the correct behaviour?
The endpoint should allow us to update the entitlements on SailPoint so that they match the ones we have changed on our own service.
What are the steps to reproduce the issue?
When trying to make changes to the entitlements on our staging environment a webhook call to the SailPoint IdentityNow API is made. However the call is unsuccessful and the IdentityNow API returns a 500 server error as shown above.
What product feature is this related to?
This relating to the IdentityNow v2024 API, specifically the v2024/access-profiles/:id endpoint.
Do you have any other information about your environment that may help?
Our staging environment is deployed in docker to an AWS EC2 instance, and it seems to fail only there. When tested locally the updates to the entitlements are propagated without any issues.
