Local Container Authentication

Version

Demo Video

Application Scenarios

Local container authentication is an authorization method designed for server environments with no fixed or frequently changing servers such as private clouds and virtual servers. It is suitable for the following scenarios:

Local machine information authentication cannot be used as machine information changes after restart (like virtual machine deployment and docker container deployment).

Public cloud authentication cannot be used (as FineBI project is deployed in an intranet environment).

Private cloud authentication cannot be used (as it is impossible to provide an authentication server with unchanged physical information).

Functions

You can use your mobile phone as a medium to perform local container authentication. The authorization process is shown in the following figure.

Notes

You need to note the following points in local container authentication:

1. FineBI project can be registered through Local Container, which is not limited by physical information. (Changes in physical information will not cause registration failures.)

2. Customers' FineBI projects (no need to open external network addresses separately) should be equipped with a mobile phone that can communicate with the external network environment.

3. After FineBI project is restarted, re-authentication is required (rescan the QR code and enter the verification code without re-uploading the Container.lic file). For details, see section "Scanning the QR Code".

4. One authorization for one FineBI project

You need to note the following points in local container authentication for clusters:

1. Cluster registration prices fluctuate based on the maximum number of registration (the number of cluster nodes required).

2. If the number of cluster nodes exceeds the maximum number of registration, registration will fail.

3. Before you register the cluster project, ensure that the time of each server is consistent.

4. If all nodes in the cluster are restarted, the FineBI project needs to be re-authenticated (rescan the QR code and enter the verification code, without re-uploading the Container.lic file). For details, see section "Scanning the QR Code".

Obtaining the Authorization File

Use the email address specified in the contract and send the registration information to FineBI business personnel (business@fanruan.com). The email format is as follows:

After the business personnel receives the email and verifies it, they will generate the Container.lic file and email it to you by.

Note: Indicate the special circumstances (if any) in the email.

Uploading the lic File

Log into FineBI as the admin, choose Manage > Registration, and click Register Now.

Select Local Container as AUTH Method, click Upload lic, and upload the Container.lic file from the email sent by the business personnel.

After successful uploading, an authentication QR code will be generated. 

Scanning the QR Code

Scan the generated QR code through a mobile browser to obtain a 6-digit verification code. Enter the verification code in the system and click Submit.

Note:

1. The QR code is valid for five minutes (refresh manually after five minutes). Ensure that the registration is completed within the specified time.

2. After scanning the code with your phone to obtain the verification code, it is best to register the project immediately (not restart the project before successful registration).

3. If the number of incorrect verification code inputs exceeds five times, the system will be locked for 15 minutes (to prevent brute force attack and high-frequency access to the interface).

Registration takes effect after successful authentication.

The Container.lic file sent by the business personnel can only be registered in one FineBI project.

To replace the FineBI project server, contact the business personnel to cancel the registration authorization of the original server. Then the new server can be registered through the Container.lic file sent by the business personnel.

Note:

If the original server is not unbound, the registration will fail when a new server is registered. A prompt pops up: The maximum licence number has been reached.

Problem

If registration fails, a prompt window pops up.

Cause

Click Details to view causes for registration failure. You can troubleshoot according to the specific cause.

Note:

In addition to the above causes for failure, other errors will be reported uniformly: The certificate content is incorrect.

When there are multiple causes for failure, all of them will be displayed in the platform.