Including Form / Workflow Data in a Provisioning Plan

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

Hi Sailors,

I’m encountering an interesting yet persistent scenario that spans multiple applications and connector types. In these cases, when a user requests access, they are required to provide additional attributes , such as Location and Unit Number , which are essential for the provisioning.

We’ve already implemented forms to handle the UI aspect, allowing users to select these additional values. The challenge now lies in passing these values into the provisioning plan effectively.

Has anyone tackled a similar use case or can suggest a approach to achieve this?

Appreciate your insights!

Thanks in Advance!
Sid

2

It seems that the only way to modify a plan is through BPR, if the values input by users are available there, the plan can be modified.

Check if you use any HTTP calls or OOTB actions, and if these values are available before provisioning.

3

Hi @sidharth_tarlapally

I had something similar where i had to pass the data from interactive forms to the provisioning plan during access request.
So i went with the entitlement request (using the HTTP Operation) & then inside clientMetadata included the data with my own set of key and values.

API: create-access-request | SailPoint Developer Community

Example,


{
    "requestType": "GRANT_ACCESS",
    "requestedFor": [
        "<<Identity ID>>"
    ],
    "requestedItems": [
        {
            "clientMetadata": {
                "NewLocation": "{{$.interactiveForm1.formData.location}}",
                "NewDepartment": "{{$.interactiveForm1.formData.department}}",
                "Identifier": "{{$.interactiveForm1.formData.identifier}}"
            },
            "id": "<<Entitlement ID>>",
            "type": "ENTITLEMENT"
        }
    ]
}

Hope this helps.