Local Container AUTH

1. Version

2. Application scenarios

Local container authentication is an authorization method designed for private cloud, virtual server and other server environments without fixed servers or frequently changed. It is suitable for the following scenarios:

• No fixed machine information: virtual machine, docker containerized deployment, machine information will change after restart. Unable to authenticate using local machine information.

• The report project is deployed in the intranet environment, and public cloud authentication cannot be used.

• Unable to provide an authentication server with unchanged physical information, Private cloud authentication cannot be used.

3. Function Introduction

Users can use mobile phones as a medium to perform local container authentication. The authorization process is shown in the following figure:

4. Notes

The following points should be noted in the local container authentication method:

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

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

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

4) After the report server is restarted, re-authentication is required. There is no need to re-upload the Container.lic  file, just re-scan the QR code to fill in the verification code. See Section 2.3.

5) The user applies for one authorization and can only register one report project.

Notes when the cluster uses the local container authentication method:

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

2) If the number of cluster nodes exceeds the "Maximum Registerable Number", the registration will fail.

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

4) If all nodes in the cluster are restarted, the report project needs to be re-authenticated. There is no need to re-upload the Container.lic  file, just re-scan the QR code to fill in the verification code. See PASection 2.3.

1. Obtain the authorization file

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

After the business receives the email, it will generate a Container.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 clicks "Manage>Registration> Version Information>Register Now", as shown in the following figure:

Select "Local Container" as the authentication method, click "Upload lic", and 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 the QR code

Scanning the generated QR code with the mobile browser/WeChat will return a 6-digit verification code, fill in the verification code into the system, and click "Submit" button. 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 you to refresh manually.

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

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

The registration takes effect after the authentication is successful. 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 company to cancel the registration authorization of the original server, and the new server can use the Container.lic file sent by the company for registration.

Note: If the original server is not unbound, when the new server uses the original server's public cloud account to register, the registration will fail, and it will 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 below:

2. Reasons for failure

Click Details to view the reasons for the registration failure, and troubleshoot according to the specific failure reasons.

Note: In addition to the above failure reasons, other unified errors are reported: the content of the certificate is incorrect.

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