Bulk Remove Tags via Search Query in Workflow

[sjoyee (Jo Yee Siang)]

Hi all.

In our use case, we would like to bulk remove tags from the identities with certain tag using the HTTP Request action with this API delete-tags-to-many-object | SailPoint Developer Community in the workflow.

I notice that when querying out the identities using search query filtering out only the identity ID, the return response is as follows, where the type value is in lower case.

[
      {
          "id": "1231111111111111111",
          "_type": "identity",
          "type": "identity",
          "_version": "v7"
      },
      {
          "id": "4561111111111111111",
          "_type": "identity",
          "type": "identity",
          "_version": "v7"
      },
      {
          "id": "7891111111111111111",
          "_type": "identity",
          "type": "identity",
          "_version": "v7"
      }
]

However, in the bulk remove API, the value for type is in upper case. "type":"IDENTITY" as follows, and will throw 500 Internal Server Error if lower case is used.

{
    "objectRefs": [
        {
            "id": "1231111111111111111",
            "type": "IDENTITY"
        },
        {
            "id": "4561111111111111111",
            "type": "IDENTITY"
        },
        {
            "id": "7891111111111111111",
            "type": "IDENTITY"
        }
    ],
    "tags": [
        "TEST_TAG"
    ]
}

Is there any suggested way in the workflow for us to directly place the return output of the queried identities in the payload for the bulk removal of tag API? Else we would need to consider using loop action and remove tag one by one for each queried identity.

Appreciate any input. Thanks!

[sushantkulkarni]

@sjoyee I’ve observed the same thing when using the bulk remove tag API, and you’re right, it will throw the internal server error for the lowercase type.

Unless there is a change in the way the API response is returned, you’d have to process the response to convert the case, which can be really tricky on a workflow step. I’m trying to think of define variable step, but even that may not be able to pull it off is what it looks like to me.

I guess you can’t avoid looping and doing it once for every user, separately, as painful as that approach seems!