Import Users

1. Version

2. Application scenarios

·       The administrator can import the organized user information table into the data decision system at one time.

·       Administrators can import user information, departments, and roles multiple times.

·       Administrators can edit, disable, delete imported users

·       Users expect platform users to be a collection of multiple datasets.

3. Function introduction

·       Create a server data set based on the user information table , and import the user information into the data decision system. After importing user information, if a user is added or deleted from the server data set, it needs to be manually imported again . A platform user can be a collection of multiple datasets.

·       When importing a dataset, if the encryption method is not switched, the previously added/imported user data will not be cleared.

The imported user data comes from the server dataset, and supports user departments with or without hierarchy.

Users can choose one of them according to their own user structure.

1. No Hierarchy - SQL Datasets

The user information table used in the example in this section has no hierarchical structure among department titles. The departments of the imported users are listed under "All Departments", as shown in the following figure:

1) Prepare user information sheet

Prepare a user information table, the table structure is shown in the following figure:

Click to download the user information table: Import users.xlsx

Note 1: When importing users, user name, name and password are required items, and other contents can be left blank.

Note 2: The BI project version before 5.1.9 only supports binding the mobile phone number in mainland China, and the mobile phone number does not need to add the area code

5.1.9 and later BI engineering versions, user mobile phone numbers can be bound to mobile phone numbers in mainland China, Taiwan, Hong Kong, Turkey, South Korea, Japan, Singapore, and Malaysia

You can choose whether to add an area code to the mobile phone number in mainland China, and you need to add the area code to the mobile phone number in other areas.

2) Create server dataset

Use third-party tools such as Navicat to import the above table into the database, and establish a data connection between the system and the database . The following will take the FRDemo database as an example.

The administrator logs in to the data decision system, and clicks "Manage > Data Connection > Server Dataset" to create a "SQL Dataset". As shown below:

Set the dataset name to "Import User ", select " FRDemo " for data connection, and the SQL statement is:

select * from import user1

2. No Hierarchy - File Dataset

Note: 5.1.9 and later BI projects support importing users through "File Data Set".

The user information table used in the example in this section has no hierarchical structure among department titles. The departments of the imported users are listed under "All Departments", as shown in the following figure:

1) Prepare user information sheet

Prepare a user information table, the table structure is shown in the following figure:

Click to download the user information table: Import users.xlsx

Note 1: When importing users, user name, name and password are required items, and other contents can be left blank.

Note 2: The BI project version before 5.1.9 only supports binding the mobile phone number in mainland China, and the mobile phone number does not need to be added with the area code.

5.1.9 and later BI engineering versions, user mobile phone numbers can be bound to mobile phone numbers in mainland China, Taiwan, Hong Kong, Turkey, South Korea, Japan, Singapore, and Malaysia

You can choose whether to add an area code to the mobile phone number in mainland China, and you need to add the area code to the mobile phone number in other areas.

Note 3: TXT / XML file can also be used, please refer to the setting method: file data set

2) Create server dataset

Save the table locally, or upload it to the %FR_HOME%\webapps\ webroot \WEB-INF\ reportlets directory of the BI project.

The administrator logs in to the data decision system, and clicks "Manage > Data Connection > Server Dataset" to create a "File Dataset". As shown below:

Set the dataset name to "Import User-File" and select the table prepared above.

Note 1: If you select the server file, select the file in the %BI_HOME%\webapps\ webroot \WEB-INF\ reportlets directory of the BI project.

If you select a local file, the file will be automatically saved to the %BI_HOME%\webapps\ webroot \WEB-INF\ reportlets \excel directory of the BI project after uploading.

Note 2: TXT / XML / remote URL files can also be used, and data set parameters are supported. For the setting method, please refer to: File Data Set .

3. Hierarchical structure - tree dataset

The user information table used in the example in this section has a hierarchical structure between department titles. The departments of imported users are shown in the following figure:

1) Prepare User Information Sheet

Prepare a user information table, the table structure is shown in the following figure:

Click to download the user information table: Import User2.xlsx

Note 1: When importing users, user name, name and password are required items, and other contents can be left blank.

Note 2: The BI project version before 5.1.9 only supports binding the mobile phone number in mainland China, and the mobile phone number does not need to add the area code

5.1.9 and later BI engineering versions, user mobile phone numbers can be bound to mobile phone numbers in mainland China, Taiwan, Hong Kong, Turkey, South Korea, Japan, Singapore, and Malaysia

You can choose whether to add an area code to the mobile phone number in mainland China, and you need to add the area code to the mobile phone number in other areas.

Note 3: When synchronizing user data sets, if the server data set is a tree data set, the parent organization of the top-level organization should be null. For the Abby user as shown in the figure below, the fid field is empty.

Note 4: It is also possible for departments without users. For example, the headquarters only has subordinate departments, but there are no direct subordinate positions and users. It is also possible to generate tree data sets and synchronize users.

2) Create SQL dataset

Use third-party tools such as Navicat to import the above table into the database, and establish a data connection between the system and the database . The following will take the FRDemo database as an example.

The administrator logs in to the data decision system, and clicks "Manage > Data Connection > Server Dataset" to create a "SQL Dataset". As shown below:

Set the dataset name to "Import User 2", select " FRDemo " for data connection, and the SQL statement is:

select * from import user 2

3) Creating a tree dataset

The administrator logs in to the data decision system, and clicks "Manage > Data Connection > Server Dataset" to create a " Tree Dataset". As shown below:

Set the dataset name to "Import User - Hierarchical", which is constructed from the dataset "Import User 2", the original tag field is "did", and the parent tag field is "fid", as shown in the following figure:

The administrator logs in to the data decision system, clicks "Manage > User> All Users", and clicks "Import User2" to configure user information. As shown below:

The specific setting items are as follows:

1. Retained Information

2. Server dataset

Select the server dataset corresponding to the user information.

3. Field names

Username, name, password, department name, job title, role name, mobile phone, and email address are the field names in the corresponding server data set.

Note 1: The user mailbox information in the user management configuration is used in conjunction with the system management email, and the data decision system can directly send emails to the user mailboxes of different platforms.

Note 2: The unselected state cannot be restored after the department and job are configured, but can only be deleted and added again.

Note 3: BI projects of version 5.1.11 and later support only the configuration of the department, but not the configuration of the title.

For BI projects prior to version 5.1.11, departments must be configured with jobs.

4. Encryption method.

Note: user information table in section 2.1 of this article , not the encrypted password in the fine_user user table .

There are two encryption methods, "built-in SHA encryption" and "custom password encryption".

1) Built-in SHA encryption

The data decision system adopts SHA256 encryption to ensure password security.

After the user customizes the password through the interface, SHA256 encryption will be performed automatically.

2 ) Custom password encryption

Custom password encryption, that is, to customize a password encryption class. The encryption method is described in the class and saved in the % FineBI %\webapps\ webroot \WEB-INF\classes folder.

The data decision system will perform SHA256 secondary encryption based on the user-defined encryption algorithm to ensure password security.

For details of custom encryption examples, see: Password encryption for simple permissions

Note: To customize the encryption algorithm, you must inherit the AbstractPasswordValidator class, and add a method to return the result of judging whether the plaintext password and the ciphertext password are consistent.

Administrators can edit, disable, and delete imported users . For details, see Adding UsersChapters 3 , 4 , 5 _