Lifecycle Event - RapidSetup Joiner & Active Directory provisioning not triggering post ID aggregation from Workday

Which IIQ version are you inquiring about?

Version 8.3

Share all details related to your problem, including any error messages you may have received.

Hello All,

I am trying to look for any lead that can help me with the below issue:
We have configured workday connector recently where any new id which is created in workday gets aggregated to SailPointIIQ and “RapidSetup Joiner” lifecycle event get triggered and at same time the account get created in xyz AD and provisioning access to it.

Earlier, this flow was working as expected but now ID is getting aggregated to SailPoint but “RapidSetup Joiner” event is not getting triggered and in AD also ID is not getting created. We can see only workday application in “Application Accounts” tab not the xyz AD application. Earlier AD application was also visible in “Application Accounts” tab.

If anyone of you have faced similar kind of issue or have any lead to find solution to this issue, it will be really helpful.

Thank you in advance!

Is Workday marked as authoritative?

Yes, workday is marked as authoritative.

Ok and is the identity marked as correlated? I’m asking because rapid setup workflows are skipping non correlated identities.

Any errors in logs?

Can you see if provisioning transaction to AD is started admin console?

Yes yes, Identities are also marked as correlated.

Let me check AD part and confirm it to you.

I don’t see any provisioning transaction to AD in admin console. For previous users, there are transactions presents but not for the new IDs (From the time we started facing this issue)

In logs, exactly what I should look for? because I don’t find anything specifically for event or AD.

validate the entry in the Configuration → RapidSetupConfiguration

there will be an entry for Workday, under that validate the what’s the value for the Joiner, once the Identity gets aggregated from WorkDay, validate if the condition specified under the RapidSetupConfiguration for matches with the same in the newly onboarded Identity.

Also, in the same configuration validate the entries for your AD Application, most likely there will be Population specified that will trigger the Provisioning of AD Account at the time of Joiner Process, confirm whether the newly onboarded Identity satisfies the condition for the Population.

Hello @Abhisinha89

It worked. Thank you soo much for your help! :blush:

@kjakubiak Thank you for looking into this matter. :blush: