We have same entitlements in different AD sources, means we have duplicate entitlements in IDN.
I have setup a workflow, when the user access is provisioned, it emails description of the entitlement to the intended user. I have used HTTP GET Request action in the workflow that gets description of dynamic entitlement (once access is provisioned) and then emails it to the user.
Issue:
The HTTP GET request action returns results from all AD sources because the entitlement value is exactly the same in all AD sources. I canât use Id or name of the entitlement as the JSON payload (provisinoig completed trigger) only has the entitlement value.
Question:
How can we restrict the HTTP GET request action to get the result only from a specific AD source? I have tried all below possible combinations but the HTTP request keeps failing.
Iâve tried this but it doesnât work as it throws ârequest failedâ error message.
FYI - Iâve tried this using the value attribute of the entitlement because JSON payload has only the value of the entitlement and not the name of entitlement.
https://tenant.api.identitynow.com//beta/entitlements?filters=value eq "{{$.trigger.accountRequests[0].attributeRequests[0].attributeValue}}" and source.id eq âidOfTheSourceFromUIâ
Iâve tried this but it doesnât work. It throws ârequest failedâ error message as shown in the attached screenshot. https://tenant.api.identitynow.com/beta/entitlements?filters=value%20eq%20%22{{$.trigger.accountRequests[0].attributeRequests[0].attributeValue}}%22%20AND%20sourceId%20eq%20%22idOfTheSourceFromUI%22
The following request url and query parameters did the trick for me. Now the HTTP GET request returns result only from a specific source as expected. Awesome
Query Parameters:
filters value eq â{{$.trigger.accountRequests[0].attributeRequests[0].attributeValue}}â and source.id eq âxxxxxxxxxxxxxxxxxxâ