Local Container AUTH

1. Version

2. Application scenarios

Local container authentication is an authorization method designed specifically for server environments without fixed services or changes such as grandmother clouds and virtual servers. It is suitable for the following scenarios:

No fixed machine information: virtual machine and dock containerized deployment, machine information changes after restart. Unable to use local machine information authentication.

In the deployment time network environment of the report project, public cloud authentication cannot be used.

It is not possible to provide a single authentication server with unchanged information, and it is impossible to use secure cloud authentication.

3. Function introduction

The user can be authorized by the mobile phone for local user authentication. The authorization process is shown in the figure below:

4. Matters needing attention

The local container authentication method has the following points to note:

1) Local container certification only supports report projects whose JAR package time is 2021-10-30 and later.

2) The local container authentication of the report project will not be restricted by physical information, and the change of physical information will not cause registration failure.

3) The client report server does not need to open the external network address, but it needs to have a mobile phone that can communicate with the external network environment.

4) After the report server restarts, re-authentication is required. There is no need to re-upload theContainer.lic file, just rescan the QR code to fill in the verification code. See Section II.3.

5) When a user applies for an authorization, only one report project can be registered.

Pay attention to the following when the cluster uses the local container authentication method:

1) The cluster registration price fluctuates according to theMaximum Registerable Amount(that is, the number of cluster nodes required).

2) If the number of cluster nodes exceeds the Maximum Registrable Quantity, the registration will not succeed.

3) Before registering the cluster project, please make sure that the time of each server is consistent.

4) If all nodes in the cluster restart, the report project needs to be re-certified. There is no need to re-upload the Container.lic file, just rescan the QR code to fill in the verification code. See Section II.3.

1. Obtaining authorization documents

Please use the email address specified in the contract to send the registration information to FineReport Businessbusiness@fanruan.com, the email format is as follows:

After the business receives the email, it will generate theContainer.lic file for the user after verification and send it to the user by email.

2. Upload lic file

The administrator logs in to the data decision system and clicksManage>Registration >Register Now, as shown in the figure below:

SelectLocal Container as the authentication method, and clickUpload lic to upload the Container.lic file in the business email. After the upload is successful, an authentication QR code will be generated. As shown below:

3. Scan QR code

Use the mobile browser/WeChat to scan the generated QR code, and a 6-digit verification code will be returned. Fill in the verification code into the system and clickSubmit. As shown below:

Note 1: The QR code is valid for 5 minutes, please complete the registration process within the specified time. After more than 5 minutes, the QR code will prompt that it needs to be refreshed manually.

Note 2: After the mobile phone scans the code and returns the verification code, it is best to register the project immediately, and do not restart the project before the registration is successful.

Note 3: In order to prevent brute force cracking of the verification code and high-frequency access to the interface, if the verification code is entered incorrectly for more than 5 times, it will be locked for 15 minutes.

Registration takes effect after successful authentication. As shown below:

The Container.lic file sent by business can only be registered in one report project.

If you need to replace the report engineering server, please contact the business to cancel the registration authorization of the original server, and the new server can use theContainer.lic file sent by the business to register.

Note: If the original server does not unbind, when the new server uses the original server's public cloud account to register, the registration fails, and the prompt: the maximum number of authorizations has been reached.

1. Phenomenon description

If the registration fails, a pop-up window will appear on the page, as shown in the figure below:

2. Reason for failure

Click on the detailed information to view the reason for the registration failure, and perform troubleshooting based on the specific failure reason.

Note: In addition to the failure reasons other than the above, other unified error: the content of the certificate is incorrect.

          When there are multiple failure reasons, they will all be displayed in the platform.