Overview
Application Scenario
This authentication method is designed for scenarios where there is no fixed server or the server frequently changes, such as the private cloud server and virtual server.
No fixed machine information: Authentication via local machine information is unavailable for projects deployed on virtual machines as the machine information changes every time the machine is restarted.
Intranet environment: Authentication via a public could is unavailable for FineDataLink projects deployed in an intranet environment.
Lack of an authentication server with fixed physical information: Private cloud authentication cannot be used.
Function Description
You can use your mobile phone as a medium for authentication. The following figure shows the authorization process.
Notes
Note the following points when using this authentication method.
1. The registration authenticated via this method is not subject to physical information changes.
2. The FineDataLink server does not require access to an external network address, but a mobile phone with extranet connectivity is necessary.
3. After restarting the FineDataLink server, re-authentication is required. You just need to re-scan the QR code and enter the verification code instead of re-uploading the Container.lic file. For details, see section "Scanning the QR Code."
4. One license can be used to register one FineDataLink project only.
Note the following points when using this authentication method for clusters.
1. The registration price for clusters varies according to the maximum registration capacity, namely the number of required cluster nodes.
2. Registration will fail if the number of cluster nodes exceeds the maximum registration capacity.
3. Before registering the cluster project, ensure that the time on all servers is synchronized.
4. Re-authenticating the FineDataLink project is required if all nodes in the cluster are restarted. You just need to re-scan the QR code and enter the verification code instead of re-uploading the Container.lic file. For details, see section "Scanning the QR Code."
Registration Procedure
Obtaining the License File
Use the email address specified in the contract and send the registration information to FineDataLink business personnel (business@fanruan.com). The email format is shown as follows.
After verifying the received email, business personnel will generate a Container.lic file and email it to you.
Needed Information | Requirement | Notes | |
---|---|---|---|
Priority contact | Contact FanRuan sales personnel in advance to confirm relevant matters and sign the contract. | / | |
Sender | Use the email address specified in the contract. | Otherwise, the registration will be rejected. | |
Recipient | business@fanruan.com | / | |
Title | Company Name Registration for FineDataLink Official Authorization Document | If you do not mark the company name in the email, the registration will be rejected. | |
Body | Basic Information | Company name: Company Name Project name: Project Name Contract signing date: YYYY/MM/DD | / |
Registration method | Local container authentication | / | |
Maximum registration capacity | Number of nodes in the cluster project | If this option is not provided, the number defaults to 1. You do not need to provide information about this item in a standalone setup. | |
Project version | Provide the minor version and JAR package information of the project. You can check the above information under System Management > Registration Management > Version Information. | / |
Uploading the License File
1. Log in to FineDataLink as the admin, choose System Management > Registration Management, and click Register Now, as shown in the following figure.
2. Select Local Container as Authentication Method, click Upload License, and upload the Container.lic file obtained in section "Obtaining the Authorization Document." After successful uploading, an authentication QR code is generated, as shown in the following figure.
Scanning the QR Code
Scan the generated QR code through a mobile browser/WeChat to obtain a 6-digit verification code. Fill in the verification code in the system and click Submit, as shown in the following figure.

The QR code is valid for five minutes. Ensure that the registration is completed within the specified time. Refresh the QR code manually if the registration takes more than 5 minutes.
You'd better register the project immediately after getting the verification code and do not restart the project until the registration is successful.
If the number of incorrect inputs of the verification code exceeds five, the input will be locked for 15 minutes to prevent brute force attacks and high-frequency access to the interface.
Registration takes effect after successful authentication, as shown in the following figure.
License Migration
The Container.lic file sent by business personnel can be used to register one FineDataLink project only.
To change the FineDataLink project server, contact business personnel to cancel the registration on the old server first, then you can register the project on a new server using the same Container.lic file.

Re-registration After Restarting the Project
The authentication will become invalid if you restart the project. In this case, you need to re-scan the QR code for re-registration. To prevent administrators from forgetting, a strong reminder function has been added in FineDataLink.
When you log in to FineDataLink as the admin with permission on Registration Management after restarting a project, the prompt "Your project registration has expired due to a project restart. Enter registration management and authenticate again." will pop up.
1. Click Authenticate to be redirected to the Registration Management page.
2. Click Re-register. A QR code with authentication information will appear. Scan the QR code with your mobile phone to receive the verification code.
3. Enter the verification code and click Submit. The re-registration will be successful, as shown in the following figure.
Registration Failure Troubleshooting
Problem
A prompt window pops up if the registration fails, as shown in the following figure.
Failure Reason
You can click Details to view the reason for the registration failure and troubleshoot accordingly.
Failure Reason | Specific Prompt |
---|---|
License Expired | Expiration Date: YYYY/MM/DD |
Version Mismatch | Certified App Version: App Version Local App Version: App Version |
App Name Mismatch | Certified App Project Name: App Name Local App Project Name: App Name |
Registration Capacity Reached | The number of cluster nodes exceeds the maximum registration capacity of the license. |
Project Content Mismatch | Certified Project Content: Project Content Local Project Content: Project Content |
License Type/Version Mismatch | The selected authentication method does not match the type of the uploaded license. |

The error message of all other errors not mentioned in the following table is "Incorrect License Format".
If the registration fails for multiple reasons, all the reasons will be displayed on the platform.