Multi-Domain LDAP Authentication (Enhanced) Plugin

6.0

V1.7.3

Added multi-domain synchronization and LDAPS functions based on the original Multiple LDAP Users Synchronization plugin.

6.0

V1.7.5

1. Optimized the synchronization speed.

2. Added some functions, including resynchronizing user types 

during user synchronization, plugin deletion clearing no configurations, supporting some special characters, and allowing users with the same name in multiple domains to be synchronized.

3. Added limitations on user type selection. Specifically, the 

Platform User type needs to be ticked before the current user 

type configuration takes effect.

6.0

V1.7.7

Supported clusters.

6.0

V1.7.9

Allowed the letter case of usernames to be unchanged.

Reserved

If a user is not in the synchronized dataset, the user information and permissions 

remain unchanged.

If a user is in the synchronized dataset (with the same username):

The user's username and permissions remain unchanged.

The user's name, password, mobile number, and mailbox are updated.

If the user's current department, position, and role exist in the synchronized dataset, they are updated.

If the user's current department, position, and role do not exist in the synchronized 

server dataset, they remain unchanged.

Clear

Delete all the platform information of manually added/imported users, including their username, name, password, mobile number, mailbox, department, position, role, 

and permissions, and you can synchronize users again.

Super admin

1. During re-synchronization, the name, mobile number, and mailbox of existing users in the platform will no longer be updated.

2. Super admins can edit the name, mobile number, and mailbox of existing users in the platform, but cannot edit the role.

3. Super admins can edit their own name, password, mobile number, and mailbox in 

Account Setting.

4. Super admins can use the Forgot Password function under System Management > System Setting > Login.

Subordinate admin

1. Subordinate admins (with corresponding permissions) can modify the name, mobile 

number, and mailbox of synchronized users, but cannot edit the role and password.

2. Subordinate admins (with corresponding permissions) can modify the name, 

password, mobile number, and mailbox of built-in users, but cannot edit the role.

3. Subordinate admins can edit their own name, mobile number, and mailbox in Account Setting.

Ordinary user

Ordinary users can edit their own name, mobile number, and mailbox in Account 

Setting.

ObjectClass

Select an ObjectClass used to store the user attribute.

Required

User Duplication   Verification Field

User duplication verification can be achieved through 

User ID or Username.

1. If you select User ID, the User ID field is synchronized. The field value of User ID is the user ID in the LDAP 

server when you synchronize users.

2. If you select Username, the Username field is synchronized. The field value of User ID is randomly generated by the system.

Required

User ID

This field is required only when User ID is selected in 

User Duplication Verification Field.

Select the UID (User ID) in the user attribute.

Required

Username

Select the username in the user attribute.

Username stored in the LDAP server cannot use 

double-byte Japanese, traditional Chinese, or Korean characters. Otherwise, the message Incorrect Username or Password is displayed if the user logs in to the system.

Required

User Type

Select BI Edit User or Platform User.

Note: Select BI Design User—Data Analysis User or BI Design User—Data Processing User in FineBI versions of 5.X.

Optional

1. Plugin of versions earlier than V1.7.9

The case of usernames is uniformly converted to lowercase during user synchronization.

2. Plugin of V1.7.9 and later versions

Add a new Username Conversion Policy function that 

allows users to select Keep Case Unchanged. If this 

option is ticked, the case of the original username remains unchanged during user synchronization.

Note:

If the external database is case-sensitive and 

historical synchronization of LDAP users has 

been performed, ticking Keep Case 

Unchanged causes synchronization failure. You need to clear the historical data and perform re-synchronization.

After configuration modification, re-synchronization may cause the loss of certain user configuration permissions. For example, if the user ANNA was originally synchronized and stored as anna, ticking Keep Case Unchanged and re-synchronizing will save the user as ANNA. In this case, 

the role configuration previously assigned to 

anna will be lost, and ANNA will not inherit the 

role configuration of anna.

Optional

You are not advised to tick this 

option if you do 

not have special 

requirements. 

Username stored in the database is in lowercase by 

default.

Name

Select the name in the user attribute.

Required

Mobile

Select the mobile number in the user attribute.

Optional

Mailbox

Select the mailbox in the user attribute.

Optional

Select other contents (batch selection supported) to be synchronized.

Note:

This function is supported in V1.8.0 and later versions. After this function is configured, data is stored in JSON format to the Fine_Extra_Properties table in FineDB.

ObjectClass

Select an ObjectClass used to store the department 

attribute.

Optional

The configuration items here 

should be left empty/be entered 

for all.

Department   Duplication Verification Field

Department duplication verification can be achieved through Department ID or Department Name.

1. If you select Department ID, the Department ID field is synchronized. The field value of Department ID is the department ID in the LDAP server when you synchronize users.

2. If you select Department Name, the Department Name 

field is synchronized. The field value of Department ID is 

randomly generated by the system.

Department ID

This field is required only when Department ID is selected in Department Duplication Verification Field.

Select the UID (Department ID) in the department attribute.

Department Name

Select the department name in the department attribute.

ObjectClass

Select an ObjectClass used to store the role attribute.

Optional

The configuration 

items here should be left empty/be 

entered for all.

Role Duplication   Verification Field

Role duplication verification can be achieved through 

Role ID or Role Name.

1. If you select Role ID, the Role ID and field is synchronized. The field value of Role ID is the role ID in the LDAP server when you synchronize users.

2. If you select Role Name, the Role Name field is 

synchronized. The field value of Role ID is randomly 

generated by the system.

Role ID

This field is required only when Role ID is selected in Role Duplication Verification Field.

Select the UID (Role ID) in the role attribute.

Role Name

Select the role name in the role attribute.

ObjectClass

Select an ObjectClass used to store the security group (department) attribute.

After ObjectClass is selected, load all security 

groups based on ObjectClass (as options in the 

drop-down checkbox of Group Selection).

Optional

The configuration items 

here should be left empty/be entered for all.

Group Name

If the Group Name attribute is selected, value of the LDAP attribute corresponding to the Group Name 

field is taken as the display value in the drop-down 

option of Group Selection.

Optional

If this field is set to empty, the drop-down option of 

Group Selection reads 

CN by default.

Group Selection

Group Department  Mapping

After the security group is selected, the group department mapping is automatically loaded into the 

mapping table, and the Department Name column 

supports manual input.

Optional

The configuration items 

here should be left empty/be entered for all.