Unable to create role with metadata

Feedback Bugs
1

What problem are you observing?

I am unable to create a role (POST /v2024/roles) with accessModelMetadata being anything other than null.

What is the correct behavior?

SailPoint’s own role API documentation (create-role | SailPoint Developer Community) insists we should be able to create roles with metadata.

What product feature is this related to?

ISC create role api (POST /roles)

What are the steps to reproduce the issue?

Try to create a role with metadata. I’ve run GET roles to grab the exact role object, remove modified id, created id, role id, and changed the role name and tried to create that exact same object but get the following error message:

400 Bad Request

{
    "messages": [
        {
            "localeOrigin": "DEFAULT",
            "locale": "en-US",
            "text": "Value of \"accessModelMetadata.attributes\" is empty or contains invalid data."
        },
        {
            "localeOrigin": "REQUEST",
            "locale": "en-US",
            "text": "Value of \"accessModelMetadata.attributes\" is empty or contains invalid data."
        }
    ],
    "trackingId": "24e51596ce20492e8b781d187a73d332",
    "detailCode": "400.1.3 Illegal value"
}
1 Like
2

Also worth noting is the POST ‘Add a Metadata to a Role’ endpoint (/roles/:roleId/access-model-metadata/:attributeKey/values/:attributeValue) does not work as documented, either.

The example used in the documentation here: update-attribute-key-and-value-to-role | SailPoint Developer Community states that we should be able to use attribute_key = ‘iscPrivacy’ and attribute_value = ‘public’. These are OOTB metadata attributes, and when I try to use POST /roles/:realRoleIdHere/access-model-metadata/iscPrivacy/values/public I get the following:

{

    "messages": [

        {

            "localeOrigin": "REQUEST",

            "locale": "en-US",

            "text": "Referenced UNKNOWN was not found."

        },

        {

            "localeOrigin": "DEFAULT",

            "locale": "en-US",

            "text": "Referenced UNKNOWN was not found."

        }

    ],

    "detailCode": "400.1.404 Referenced object not found",

    "trackingId": "808c8f6959aa4c008602e7b2078a5586"

}
3

Hi Dominick,
I’m facing the same issue, have you found any solution?

4

It looks like you can PATCH a role’s metadata instead to get around the endpoints I mentioned above.