Project Registration Method Selection

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.

1. The physical information of the server where the FineDataLink project is deployed can be flexible.

2. You do not need to provide an additional server with fixed physical information as the authorization server.

3. The FineDataLink server can be located in an intranet environment and you do not need to open ports for external network access.

1. A formal license file is valid for only one FineDataLink project.

3. If you need to change the authorized project, contact business personnel for license migration.

Public Cloud Authentication

You may want to register multiple projects without exporting project information repeatedly or setting up a local authorization server.

FanRuan provides a public cloud authorization server. You can initiate authorization requests by filling in authentication information, and send the requests to the public cloud authorization server for unified authentication.

1. The physical information of the server where the FineDataLink project is deployed can be flexible.

2. You do not need to provide an additional server with fixed physical information as the authorization server.

3. You can register any FineDataLink project if the IP address of the FineDataLink server is not restricted when you apply for the account credential.

4. You can complete registration migration without contacting business personnel.

The FineDataLink server must be able to connect to the FanRuan authorization server via the public network, otherwise public cloud registration cannot be used.

Local Machine Info Authentication

You can obtain the MAC address and machine code of the server where the FineDataLink project is deployed by exporting an RIF file.

You can complete the registration by binding the MAC address and machine code of the server where the FineDataLink project is deployed to the authorization server.

The FineDataLink server can be located in an intranet environment and you do not need to open ports for external network access.

1. The physical information of the server where the FineDataLink project is deployed must be fixed.

2. A formal license file is valid for only one FineDataLink project.

3. If you need to change the authorized project, contact business personnel for license migration.

Private Cloud Authentication

If the FineDataLink project is deployed on a virtual machine or cloud platform, the physical information of the server is not fixed.

In this case, you can use a server with fixed physical information as the authorization server.

You simply need to bind this server address to the FineDataLink project during registration.

1. The physical information of the server where the FineDataLink project is deployed can be flexible.

2. A single authorization server can authorize multiple FineDataLink servers within the allowed registration capacity.

3. When using private cloud authentication for a cluster, you do not need to send the registration information of each node to business personnel.
4. To change the FineDataLink server, you do not need to reapply for an authorization document. You only need to ensure that the machine where the FineDataLink server is located can connect to the authorization server over the network.

1. The procedure is complex.

2. You need to provide an additional server with fixed physical information as the authorization server.

3. The FineDataLink server must be able to access the authorization server.

4. The authorization server must remain online. Otherwise, registration will fail. If you close Server.exe, the FineDataLink project will be in an unregistered state when you restart Server.exe, requiring re-registration.

Dongle Authentication

For large-scale projects, the same FineDataLink project may need to be deployed on multiple servers.

In some cases, you may be unable to provide the physical information of the machine where the FineDataLink project is deployed and do not want to set up a local authorization server.

In these cases, you can use the registration method authenticated via the dongle, which authorizes the project by binding the FineDataLink project name to the encryption lock.

The FineDataLink server can be located in an intranet environment and you do not need to open ports for external network access.

1. The procedure is complex.
2. The encryption lock must remain plugged into the server. Once the lock is removed, the registration will become invalid.
3. This authentication method relies on a physical encryption lock (similar to a USB drive), which is difficult to manage and store.
4. This authentication method does not support cluster deployment, macOS, or projects deployed via FineOps.