Inbound Provisioning from CyberArk Cloud Directory

You can provision users from your enterprise source directories (CyberArk Cloud Directory or any source Active Directory instances connected to CyberArk Identity) to one or more target Active Directory instances and assign the right set of access based on roles.

Source Target

CyberArk Cloud Directory

AD

The following users are considered for provisioning:
Users created in CyberArk Cloud Directory.
Users created in AD directory which are configured to CyberArk Identity.

You can define synchronization schedules to synchronize user data from source directory to target Active Directories.

Prerequisites

Before you start configuring inbound provisioning to AD targets, you need to do the following:

  • Installed the CyberArk Identity Connector.

    The CyberArk Identity Connector is required to provision users to AD target directories.

    See Install the CyberArk Identity Connector.

  • Stored the domain administrator account to CyberArk Identity.

    This step is only required if the CyberArk Identity Connector is not run by a domain administrator. See Manage domain administrative accounts.

  • Populated the relevant user data in your data source.

Expand the following procedures for more information about provisioning user data from Cloud Directory to Active Directory.

Add CyberArk Cloud Directory as a data source

You have to add CyberArk Cloud Directory as a data source before you can provision users form it to a target directory source.

  1. Log in to Admin Portal.
  2. Click Settings > Users > Inbound Provisioning.
  3. Click Add Source (on the Sources tab) to define the Cloud Directory service information.

    The Provisioning Source window opens.

  4. Select Cloud Directory from the Source drop-down menu.

  5. Select the Enable check box to enable the feature.

    You can configure the feature first, then enable it when you are ready.
  6. Enter a Name for this source.
  7. Click Save.

    Your configured source displays in the Sources table.

Define provisioning rules

Define provisioning rules to identify users, map user attributes, and other important provisioning configuration. You can define more than one rule for each source. For example, you might use a single rule if you are provisioning all users from Cloud Directory to a single AD OU, or multiple rules if you want logical groupings of users in Cloud Directory to have different target AD OUs.

You can mix rules that have different target directories. For example, you could create one rule that provisions full-time employees to AD and another rule that provisions contractors to another AD.

You must first add and configure a source before you can define the rules.

Step 1: Add a new rule

  1. From Settings > Users > Inbound Provisioning, select Cloud Directory and then click Actions > Add Rule.

  2. Enter a Name for this rule.

  3. Select a Provisioning Rule Mode.

    Mode Description
    Active Makes a rule active. Not recommended until you have finished all configurations. You must activate a rule before synchronizing.
    Preview Sets the rule in preview mode. Select this option for a production environment to verify the user mapping between Cloud Directory and the target directory before you make the rule Active.
    Inactive Sets the rule as inactive. Recommended until you have finished all configuration steps. You can come back to this option and activate the rule when you are ready.

Step 2: Define the users to which the rule(s) apply

Select the Source Selection Rule to define the users to which these rules apply.

  1. Select one of the following from the Source Selection Rule drop-down:

    1. All Users - Select this option to choose all users.
    1. Specific Organization - Select this option to choose a specific organization. Click Add to select the required organization.

  2. Select one of the following from the Second Level Source Selection Rule drop-down:

    1. All Roles - Select this option to choose all roles. The roles will be based on the first Source Selection Rule. For example, if you select any specific Org(s), all roles will be related to the selected Orgs.

    2. Specific Roles- Select this option to choose a specific role. Click Add to select the required role.

      1. Repeat above sub-steps until you have added all relevant roles and click Next.

Step 3: Define the target directory that you want to provision to.

  1. Select the relevant forest from the Target drop-down menu.

    When you select the forest, CyberArk Identity looks for the stored domain administrator account and shows a warning message if one is not available (unless the CyberArk Identity Connector is run by a domain administrator). See Manage domain administrative accounts.

  2. Select the relevant Domain.

  3. Select the relevant Domain Controller.

  4. Select the relevant and click Next.

Step 4: Map the attributes

  1. Review the required and automatically mapped attributes.

    You can delete optional attributes. You also have the option to map additional attributes.

  2. (Optional) Click Add and select the Target Attribute (attribute name in Active Directory) to add more attributes.

    • If there is only one match in Cloud Directory, then no corresponding source attributes are displayed; click Add again to add the attribute and view the mapping in the table.
    • If more than one source attribute can be mapped to the selected target attribute, then select a corresponding Source Attribute (attribute name in the data source) from the drop-down list; click Add again to add the attribute and view the mapping in the table.

      Continue mapping attributes until all necessary attributes are mapped.

    • You can edit the attribute in the Target Attribute column to map custom AD attributes to source attributes.

Step 5: Configure additional provisioning rule options

  1. Click Next to configure additional provisioning rule options.

  2. (Optional) Configure the following attribute options.

    Option Description
    Set user’s manager attribute If enabled, users’ manager attributes in Cloud Directory are synchronized to the target directory.
    Disable user in AD if user account status is suspended. If enabled, users with the terminated employment status in Cloud Directory are automatically disabled in the target directory source.
  3. Specify the Password Type for new user accounts.

    If you select Static Password from the drop-down list, then the system uses the same password for all new users.

    Make sure the password meets the complexity requirements set via policy for the target groups. If the password does not meet the complexity requirements, you will see the error UnableToSetPassword in the sync report.

    Provide the following information:

    Field/Option Description
    Password Specify the password to be used for all users.
    Require password change at next login

    If enabled, new users will be required to change their passwords after the initial log in. Disabled by default.

    See Password Synchronization for more details.

    If you select Generated Password from the drop-down list, then the system randomly generates different passwords for each new user.

    Provide the following information:

    Field/Option Description
    Require password change at next login If enabled, new users will be required to change their passwords after the initial log in. Disabled by default.
    Delivery Options

    Select the email address to which you want the auto-generated password sent.

    This is to help in your new employee onboarding process. When new users are created in Active Directory, an email will be sent to the specified address with the credentials for those users.

    • Send password to email address

      Enter the email address to which you want the password sent.

    • Send password to user’s manager

      Sends the password to the manager’s email address. Ensure that you have the email address specified in the data source.

    • Send password to user’s personal email

      Sends the password to the user’s email address specified in the data source.

      If Password sync feature is enabled then the password is not sent to the user's email.

      If you have more than one option selected, the password is sent to all the selected email addresses.

Step 6: (Optional ) Map users to AD groups.

  1. Enable the Add users to groups check box.

  2. Select the Add button within the Active Directory Group Options area. The Add Active Directory Group window opens.

  3. Confirm that the appropriate target group is selected.

  4. (Optional for AD) Select Assign user to an OU upon termination if you want to specify the organizational unit (OU) in which terminated users will be placed.

    If you do not enable this check box, then terminated users will remain in the current OU.

    Selecting this option requires enabling the Disable user in AD if user account status is suspended option. Both options must be enabled to successfully assign users to an OU upon termination.

    Enter the group name into the Search box to find the group.

  5. Select the group and click Add.

  6. Select Re-evaluate Group Memberships to remove users satisfying the inbound provisioning rule from previous group assignments and add the users only to the groups specified.

    For example, you might have separate inbound provisioning rules configured to provision users in a sales source group to a sales AD group, and a marketing source group to a marketing AD group. If a user moves from the sales organization to the marketing organization, the user should be removed from the AD sales group so that the user's access is appropriate for just marketing, not marketing and sales. Selecting Re-evaluate Group Memberships would remove the user from the sales group when the inbound provisioning rule for the marketing source group runs.

    Re-evaluate Group Memberships removes users from all previous AD group assignments, regardless of whether the assignment was from inbound provisioning or configured manually. This might have unintended consequences for application access, authentication policies, device management, etc. Verify that your users only need the access granted to the AD groups specified in the inbound provisioning rule.

Step 7: Map Provisioning Groups to Active Directory Groups.

Provisioning Groups can be used to collect users and map them to specific AD Groups.

  1. Enable the Map Provisioning Roles to Active Directory Groups check box.

  2. Select the associated Add button.

  3. Select the Provisioning Role Name from the drop-down.

  4. Confirm that the appropriate target is selected.

  5. Enter the group name into the Search box to find the group.

  6. Select the group and click Add.

Step 8: (Optional for AD) Select Assign user to an OU upon termination if you want to specify the organizational unit (OU) in which terminated users will be placed.

If you do not enable this check box, then terminated users will remain in the current OU.

Selecting this option requires enabling the Disable user in AD if user account status is suspended check box. You need to enable both options to successfully assign users to an OU when the user is suspended in the Cloud directory or disabled in the source AD.

Step 9: Finalize the rule(s)

  1. Click Save to save the rule configuration.

    The provisioning rule has been configured and the rule is listed in the Sources table.

  2. Click the rule to change its status if you did not already set the rule to Active.

  3. Click Save.

  4. Define additional provisioning rules as needed.

    You can define more than one rule for each source.

Edit Cloud Directory as a data source in the Admin Portal

  1. Log in to the Admin Portal.

  2. Click Settings > Users > Inbound Provisioning.

  3. Click the row associated with Cloud Directory.

    The Provisioning Source page opens for edits. Complete your edits and return to the Inbound Provisioning page.

  4. Click a rule associated with Cloud Directory.

    The Inbound Provisioning Rule page opens for edits. Complete your edits as needed.

Password Synchronization

You can sync and maintain the same passwords between CyberArk Identity and multiple AD instances. You can update your password in theCyberArk Cloud Directory, and the password will be automatically updated in the Active Directory. For example, you can synchronize passwords from CyberArk Cloud Directory to AD or AD1 or AD2 but cannot sync passwords from AD to Cloud Directory.

The passwords will be only synchronized if the password policies between the Cloud Directory and AD domains are the same.

Enable Password Synchronization

Go to Core Services > Policies > User Security Policies > User Account Settings > select Yes from the Enable password sync to target Active Directory instances drop-down.

When the Password Synchronization is enabled:

  • Once the user is provisioned in the target AD from Source AD or Cloud Directory, the user's password is stored and updated in the target AD.

  • Password for cloud users who are provisioned in AD will be automatically synced when you:

    • Log in for the first time and change the password.

    • Change the password from the user portal.

    • Change the password on expiry.

    • Change the password by following the Forgot Password flow.

    • Change the password as part of the Require password change at next login.

    • Admin changes the password of any user.

  • When a user is provisioned from a source AD to Target AD, a Static or Generated Password is set as per the settings by the admin.

  • Password sync applies to both Cloud to AD and AD to AD. The cloud password will be synced to the target AD.

  • If AD1 is connected to CyberArk Identity, and AD1 users are getting provisioned to target AD2, then:

    • AD1 passwords will be synced to AD2 when you update the password in AD1 through Identity.

Synchronize data

After you have configured the data source and provisioning rule, you are ready to synchronize user data from Cloud Directory to your target directory. You have the option to manually trigger a full or incremental sync or schedule incremental syncs. Full syncs are time and resource intensive so it must be triggered manually; we recommend doing it only when necessary.

For the initial sync, you must perform a full one.

Mapping custom Cloud Directory attributes

You can use the Admin Portal to run a script mapping Cloud Directory custom fields to relevant Active Directory attributes.

In the event of a conflict between the attribute mapping table and the script, the script has priority.
  1. Log in to the Admin Portal.

  2. Click Settings > Users > Inbound Provisioning.

  3. Select the provisioning rule for which you want to add the script.

  4. Click the Attributes tab.

  5. Confirm that the Use Attribute Mapping Script checkbox is enabled.

  6. Click Load Sample to load the sample script.

  1. Update the script as necessary for your purpose.

    Custom attributes are available in the Script Help window under SourceUserRecord.

    For example, resolve DisplayName conflicts by using the checkValueExists function to see if the DisplayName already exists in AD. If checkValueExists returns True, create a new function to create a unique DisplayName for the user you are trying to provision.

    Refer to Conflict resolution for more information about resolving conflicts with scripting.

  2. Click Save.

    When a synchronization between Cloud Directory and Active Directory is triggered, the script runs automatically.

Click Closedhere for an example of a script mapping the custom data source attribute divison to the target attribute Division.

trace("Starting script...");







var sc = SyncContext;



sc.SkipUserSync = false;







trace(sc.SourceUserRecord.CustomProperties.Dump());







sc.TargetUserRecord.Company = "My company name";



sc.TargetUserRecord.DisplayName = sc.SourceUserRecord.displayName;



sc.TargetUserRecord.Division = sc.SourceUserRecord.CustomProperties.Get("division");



if(sc.SourceUserRecord.address2 != null) {



    sc.TargetUserRecord.StreetAddress = sc.SourceUserRecord.address1 + ", " + sc



.SourceUserRecord.address2;



} else {



    sc.TargetUserRecord.StreetAddress = sc.SourceUserRecord.address1;



}