What problem are you observing?
When we attempt to patch the revocationRequestConfig or the accessRequestConfig attributes for roles with a null value we receive a 500 error.
What is the correct behavior?
This should work correctly, as it does with Access Profiles and in line with the API documentation which states that these attributes are nullable - patch-role | SailPoint Developer Community
What product feature is this related to?
This is the same for both BETA and V3 APIs for ISC
What are the steps to reproduce the issue?
Making a PATCH request to a role with the body below will replicate the 500 error:
accessRequestConfig
[
{
"op": "replace",
"path": "/accessRequestConfig",
"value": null
}
]
revocationRequestConfig
[
{
"op": "replace",
"path": "/revocationRequestConfig",
"value": null
}
]
Do you have any other information about your environment that may help?
This is not environment specific.