Access Request Submitted trigger is not firing

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

I have followed the below post steps and created a workflow

The client does not have an Adaptive Approvals license, so I implemented the solution by subscribing to the trigger and using an external workflow.

This was working correctly about couple of week ago. However, when I tested it recently, the trigger no longer appears to be working. When I submit an access request, neither the workflow nor the event trigger is being invoked.

I am unsure what has changed. Have there been any recent updates or changes that would prevent this workflow approach from working in tenants that do not have an Adaptive Approvals license?

Any insights or suggestions would be greatly appreciated.

2

Are there any filters on your trigger? You could create a small workflow with the Access Request Submitted trigger and no filter, submit a request, and see if it fires. If not, then that sounds like a support case is needed.

Matt

3

Yes, i created a basic workflow woth jist a trigger and http step, and its nof firing for that as well

4

Hello @ravikiran_ch, this might be the bearer token issue. What I have seen is, if we edit the even trigger to update the filter we need to re-enter the bearer token. If you have that token copied somewhere then try to re-enter that if not create a new bearer token and try

5

Nothing in SailPoint Identity Security Cloud generally “breaks” workflows that rely on Access Request Submitted triggers purely because of the lack of Adaptive Approvals license.

6

Hi @ravikiran_ch I would suggest,

  1. double check your integration URL if you have updated correctly in the workflow and

  2. Bearer token is the correct one in the subscription

  3. Enable status of subscription.

    Are you able to fire other trigger i.e. Access request decision or try other response required type trigger (access request dynamic approver)?