We have a multi domain AD source setup that connects to 3 different domains based on entity. We want to use this single source for birthright. If someone is onboarded in location A, they are created in domain A; if location B, creation in domain B etc. What is the recommended approach, shall we create 3 separate sources and manage provisioning or is it possible to do it via single multi domain source? Also, we need to trigger PowerShell scripts per location and we have some other processes to call APIs on some target systems like ServiceNow.
If we can use multi domain source, I assume it might require before provisioning rule too?
Hi Sidhant, I have the same scenario. I manage perfectly with 3 sources, one for each domain. About the powershell script you will have to use the after operation rule for AD connector. As you will have 3 sources, you can develope only 1 rule, and inside check which source called it. So if you have to mantain code along time, it will save you from keeping 3 rules up to date. Same for the API call, you may have to configure a workflow. You can deduct from which source it cames (perhaps inspecting the provisioning completed trigger), and perform the logic in one place.
1 Like
Is it possible to do it with just 1 multi domain source or we will have to use the individual sources?
@sidhantpandey, You could potentially do it with one source and use a rule or something like a lookup transform to set the DN on the provisioning policy, however, it might be easier and cleaner to manager as separate sources as advised by @jsosa
1 Like
Thanks @jsosa and @Irshaad_Laher_WS for your response!
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.