This article applies to:
OS: Windows
Product edition: inSync On-Premise
Overview
In most environments, AD forest structure is implemented. Users across AD domains and trees are added as members to the security groups to control the access to the resources. This article describes the procedure to import cross-main AD users using inSync AD Mapping.
❗ Important
AD design limitations do not allow importing cross-forest AD users.
Import cross-domain AD users
The procedure to import the cross-domain AD users is explained based on the following scenario:
Forest root domain: Contoso.local
Child domain of Contoso.local: Child1.Contoso.local
Universal security group created inside Contoso.local: DruvaForestUsers
In Contoso.local, users from Child1.Contoso.local are added as members to DruvaForestUsers group.
Requirement: Druva inSync AD Mapping must be created to import all the users from DruvaForestUsers group
Steps
Register an AD server on inSync Management Console
Create an AD mapping
Import AD users
Step 1: Register an AD server on inSync Management Console
Login to inSync Management Console.
From the menu, go to Manage > Deployments >AD/LDAP.The AD/LDAP page is displayed .
Open the Accounts tab and click Register AD/LDAP Account.
On the Register AD Account window, enter the following field values and click OK.
Host: FQDN or IP address of the AD server from the Contoso.local domain
Port: 3268 (Enter 3269 only if secured)
Use secure connection: Select only if the AD server is configured for secure communication
Username:Domain or username from the Contoso.local domain
Password: Account password of the domain or username from the Contoso.local domain
Step 2: Create AD Mapping
Login to inSync Management Console
From the menu, go to Manage > Deployments >AD/LDAP.The AD/LDAP page is displayed .
On the Mappings tab of the AD/LDAP page , click New Mapping.
Click the Switch to manual AD/LDAP filters link.
On the Create AD/LDAP Mapping window, enter the following field values and click Next.
AD/LDAP mapping name: Name for the AD Mapping
AD/LDAP Server: Select the AD server from the drop-down list.
Base DN: Part of the base domain name that is common across the domain names of the users that are members of the AD security group.
Name to be used for creation: Username based on the organizational nomenclature.
Organizational unit: Keep this field blank.
AD group: Domain name of the AD security group (For example, CN=DruvaForestUsers,OU=TestOU,DC=Contoso,DC=local)
Department: This field is optional
Country: This field is optional
Step 3: Import AD users
Import all the cross-domain users (in this case Childuser1 and ContosoUser1 as evident from the illustration below) configured as a member of DruvaForestUsers security group.