I hope this message finds you well. I am currently working on a project involving two sources that represent two domains under the same forest:
Source 1: AD Domain 1
Source 2: AD Domain 2
In the current setup, the following rules apply during the joiner process:
a) If an identity has the identity attribute “company”=“A”, an active account is automatically created on Source 1 under the OU=Active User of AD Domain 1. b) If an identity has the identity attribute “company”=“B”, an active account is automatically created on Source 2 under the OU=Active User of AD Domain 2.
I am seeking suggestions on how to implement the following flow for a transfer case where the identity attribute “company” of a user changes from “A” to “B”. The required steps that must be satisfied to correctly implement the transfer case are:
The account must be disabled on Source 1 (AD Domain 1) and moved from the OU=Active User to the OU=Disabled User of AD Domain 1.
A new account must be created for the user in the OU=Active User of Source 2 (AD Domain 2).
What is the best way to implement the aforementioned steps 1 and 2?
Thank you in advance for your support and suggestions.
Thank you for your response. Your suggestion makes sense to me. However, I have an additional requirement:
For step 2, besides disabling the account, I also need to move the user from the OU=Active User to the OU=Disabled User of AD Domain 1. For step 3, I need to create the user in the OU=Active User of AD Domain 2.
Can I still proceed with a workflow for these additional conditions?
To move User OU to Disable OU you can configure Disable Account Provisioning Policy in SailPoint AD Source. Once user account disabled it automatically move to Disable OU.
As Phil said you can use create account provisioning policy for setting password. if you want to customize the password then you need to write generator rule based upon your password requirements and customize New Account Provisioning email template with password setup instructions for AD Source.