My team and i are trying to implement access request restriction as per this document Limiting External Access Requests.
We are looking at the option number one which is the API option. Basically we want to set the “approvalsMustBeExternal": true. However, this doesnt seems to be working. We have tried using just the body in the doc as docmented but still no luck. We have also tried doing a GET request on the access request config and pass the response of the GET request after updating the field but still no luck.
First error we got was :
{
"detailCode": "400.1 Bad request content",
"trackingId": "",
"messages": \[
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The request was syntactically correct but its content is semantically invalid."
},
{
"locale": "und",
"localeOrigin": "REQUEST",
"text": "The request was syntactically correct but its content is semantically invalid."
}
\],
"causes": \[\]
}
And the second error we got was:
{
"detailCode": "500.1 Downstream error",
"trackingId": "",
"messages": \[
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "A call from this server to another component has failed."
},
{
"locale": "und",
"localeOrigin": "REQUEST",
"text": "A call from this server to another component has failed."
}
\],
"causes": \[
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "Failed to update Configuration."
}
\]
I have also tried another body where i removed all the null values completely in the payload.
Also i have tried another body where i populated the null values with actual values from a user in my tenant but still all resulted in an error. You can try this in your tenant and let me know if that endpoint works with any body you try it with pls
Hello Vidya,
I tried exactly what you posted and still got the below error. i can confirm my tenant is up and running and other apis are working fine. Can u pls help verify by testing this in your sandbox tenant just so we verify the api endpoint is not broken.
@Otunba_skillz This seems SailPoint has added additional dependency and hence the old one is not working, I will try to check in my non prod env. and see if it works.
@Otunba_skillz Some how in one of my new tenant, external approvals is already set to true. I am not sure who did it since many people use that common tenant.
But i tried to modify it with various versions of JSON, i am also getting the same semantically incorrect error. I am trying to reach out to others to see if they have any details about it
I was able to get it to work with this Python script you shared. Thanks alot for this. Not sure why it didn’t work with postman but only with the script
Hello Vidya,
I finally got it to work in Postman by changing the collection to V2025. So both the script and Postman works fine in our Dev Tenant. However, the same change is not working in our Production Tenant. Be it the python script or the API collection, none of them is working for our Production Tenant. Below is the error message i am getting. Any help thoughts will be appreciated
{
"detailCode": "404 Not found",
"trackingId": "22xxxx37ef204ca98xxxxxx",
"messages": \[
{
"locale": "und",
"localeOrigin": "REQUEST",
"text": "The server did not find a current representation for the target resource."
},
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The server did not find a current representation for the target resource."
}
\],
"causes": \[\]
