LDAP as Identity Source

IDaaS supports multiple third-party systems as identity sources. It also supports enterprise internal LDAP directories as IDaaS identity sources, keeping organizational and user information synchronized with LDAP for unified management and data consistency.

Prerequisites

• The IDaaS public cloud service can access the LDAP directory service. If the LDAP server has network policies, add the IDaaS public cloud service IP (47.92.171.137) to the network whitelist.
• Administrator permissions for the IDaaS Enterprise Center.

Procedure

1. Log in to the IDaaS Enterprise Center, choose Users > Identity Source Management from the top navigation bar, click Add Identity Source, and select LDAP.

   

2. Customize the identity source name, fill in the host, TCP port, and other parameters as prompted, then click OK to save.

3. Enter the detail page of the newly created identity source to view or update the Basic Configuration, including connection parameters and synchronization mechanism.

   

4. Switch to the Optional Configuration tab. It is recommended to keep the default values or adjust them according to the interface prompts.

   

5. After configuration, switch to the Advanced Configuration tab. It is recommended to keep the default values or adjust them according to the interface prompts.

   

   Parameter	Description
   Select Root Organization	The location of the organization node synchronized to IDaaS.
   Organization Matching Policy	Match organizations by mapping attribute names in IDaaS and the LDAP identity source. Multiple matching rules are supported, such as matching LDAP directory organization codes with IDaaS organization codes.
   Create Organization	Default is Yes.
   Update Organization	Default is Yes.
   Delete Organization	Sets how IDaaS handles an organization after it is deleted in LDAP. Supports disabling, retaining, or deleting the organization.
   User Matching Policy	Match users by mapping attribute names in IDaaS and the LDAP identity source. Multiple matching rules are supported, such as matching LDAP directory user unique attributes with IDaaS user unique attributes.
   Create User	Default is Yes.
   Update User	Default is Yes.
   Delete User	By default, users are disabled (i.e., when a user is deleted in LDAP, the user is disabled in IDaaS). You can also retain or delete users.
   Safety Threshold Adjustment	Sets the maximum threshold ratio for changes such as deleting users, deleting organizations, or changing organization hierarchy in the upstream identity source. Threshold = (Difference between platform-recovered data and this recovery / Recovered data) × 100%. If the upstream identity source disables or deletes data exceeding the threshold, the platform will not perform the disable or delete operation.

6. After configuration, switch to the Object Model tab, select Mapping Definition, and complete the attribute definition and mapping according to actual requirements. Key parameters are described below.

   The object model supports mapping attributes of users and organizations from the LDAP identity source to IDaaS user and organization attributes. After configuration, user and organization attributes are recovered from LDAP into IDaaS.

   

   • Execution Mode: Sets when the attribute needs to be mapped.
     • Do Not Map: The attribute will not be synchronized to IDaaS.
     • Create: The attribute is synchronized only during creation.
     • Update: The attribute is synchronized only during update.
     • Create and Update: The attribute is synchronized during both creation and update.
   • Transformation Mode: Sets how the attribute is mapped.
     • Auto Transform: Synchronize the value as-is from the identity source.
     • Script Transform: Use this when the value from the identity source does not meet the required format. Refer to Script Mapping Methods.

7. After the object model is configured, click Execute Synchronization to run the synchronization immediately.

   TIP

   If the synchronization mechanism in the basic configuration is set to scheduled synchronization, there is no need to manually execute the synchronization task here.

8. After execution, switch to the Synchronization Events page to view all synchronization tasks for this identity source. Click Details under the Operation column to view the import results, or go to the Users > Users and Organizations page to view the imported data.