Local Machine Information Authentication

Version

Demo Video

.

Functions

Local machine information authentication is the most common authentication method, with simple operations and great convenience.

The physical information of the report server is fixed. You can export the RIF file to obtain a MAC address and machine code to generate a LICENSE file with unique identification.

Notes

1. Local machine information authentication requires the physical information of the report server to be fixed. If it is not fixed, this registration method is not applicable.

For example, if you deploy the report project in a virtual machine environment where the physical information may change, registration failure occurs. You need to use other registration methods.

2. A formal LICENSE file can only be registered once on a machine. If you want to register multiple projects on the same machine, you need to purchase multiple LICENSE files.

3. A formal LICENSE file is only applicable to one server. If you want to change the server, you need to migrate registration information.

4. After FineReport 9.0 is upgraded to V10.0 on the same server, you need to migrate registration information. You are advised to use Authorization Migration Plugin.

5. You need to ensure that the project uses JDK 1.8 and the minor version needs to be JDK 8u200 or later.

6. The MAC address cannot be set to empty (Registration fails in this case as the official LICENSE file forcibly authenticates the MAC address.) or unlimited.

Confirming the Project Name

Go to the path %FR_HOME%\webapps\ of the report server to confirm the project name of web. The default name is webroot.

You can modify the project name as needed before registration. It cannot be modified after registration.

Note:

1. Modify the project name with caution, because changing it may affect the settings such as the hyperlink of a template.

2. To change the project name is to change the name of this folder. After modification, the address for accessing the project becomes http://IP address:Port number/Project name/decision.

Exporting Registration Information

Start the server of the FineReport project, log in to the decision-making platform as the admin, and choose System Management > Registration Management.

Click Register Now on the Version Information tab page, select Local Machine Info as the authentication method, and click Export Registration Information.

The exported file name is RegistrationInformation.rif, and the file stores the version information of the report project.

Obtaining the License File

Use the email address specified in the contract and send the registration information to FineReport business personnel (business@fanruan.com) who will assist in generating the license. It may take a while. This method is applied to all FanRuan projects. The email format is shown as follows.

After verifying the received email, business personnel will generate a FanRuan.lic license file and email it to you.

Note:

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

Uploading the LIC File

Log in to the decision-making platform as the admin, choose System Management > Registration Management, and click Register Now.

Select Local Machine Info as the authentication method, click Upload License, and upload the obtained FanRuan.lic file.

The registration is successful if the operations above are correct.

Note:

The FanRuan.lic file will be automatically saved under the path %FR-HOME%\webroot\WEB-INF\resources of the current project.

1. Go to the path %FR_HOME%/webroot/WEB-INF/resources and delete the FanRuan.lic file.

2. Restart the FineReport project.

In versions earlier than FineReport 11.0.18, if registration fails, a prompt window pops up: Registration failed, please re-register.

In FineReport 11.0.18 and later versions, the prompt for registration failure has been optimized. If registration fails, a prompt window pops up with the specific causes and solutions or troubleshooting steps.

In a Standalone Environment

If registration fails, a prompt window pops up with the specific causes. You can click Details to view solutions or troubleshooting steps.

You can click Back to return to the registration management page.

In Registration Information, information about registration failure and the causes is displayed. You can click View Error Details to view solutions or troubleshooting steps. 

In a Clustered Environment

If registration fails, the causes may vary due to different nodes. A prompt window pops up with the specific causes of failure for each node. You can click Details to view solutions or troubleshooting steps.

You can click Back to return to the registration management page. In Registration Information, causes of failure for each node are displayed in a list format. You can click View Error Details to view solutions or troubleshooting steps.

Summary of Causes

The summary of causes of registration failure are shown as below. You can troubleshoot the problems based on specific causes and error details.

Note:

1. In addition to the following causes of failure, other errors are reported uniformly: The certificate content is incorrect.

2. If there are multiple causes of failure in a registration process, only the cause of the first failure is displayed.

The reminder appears 15 days before the license expires. Once the reminder period is reached, super admins receive the platform notification every time they log in to the platform.

The content indicates that your authorization license will expire in N days, please re-authorize as soon as possible.