Workflows HTTP Request

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

I am working on building a workflow that will trigger an access request to remove an entitlement based on a form that is submitted. I have been able to to get the api call working in Postman. When I add it to the step http request I am getting an error with 0 information other then the call failed.

This should of been a fairly straight forward workflow. However the way that the HTTP Request action works seems to have changed. It is not forcing me to use Parameter storage which I have my own credential manager configured. I am not getting any options to point to the PTA in order to grab the client information.

{25C7A4EC-5165-4304-A436-479FA2C68F03}
{25C7A4EC-5165-4304-A436-479FA2C68F03}390×562 9.01 KB

Then for the request:

{90B32598-C0F2-407E-9FCC-B142935C1E89}
{90B32598-C0F2-407E-9FCC-B142935C1E89}376×1082 23.7 KB

I have tried to pass the json paths a number of ways with no luck.

{
    "requestType": "REVOKE_ACCESS",
    "requestedFor":"{$.interactiveForm.formData.networkId}",
    "requestedItems": [
        {
            "comment": "No longer needed was assigned another license",
            "id":"{$.interactiveForm.formData.m365License}",
            "type": "ENTITLEMENT"
        }
    ]
}

Has anyone else seen this odd behavior? How did you work around it?

2

Hi @mpotti

When referencing variables, you need to wrap them like so {{}}, so for example in your case: {{$.interactiveForm.formData.m365License}}

I would also double check your variables to be sure you are getting the correct data in a defineVariable step before. requestedFor requires an array of strings, so I would make sure your networkId variable matches that format.

But other than those two things, I think your request looks correct!

3

@mpotti did you try to adding “requestedFor.$” and in “Id.$”?

4

Thank you that fixed it.