Public Cloud Authentication

Version

Demo Video

Application Scenarios

You may need to register multiple projects but don't want to set up an authorization server locally, which makes it troublesome to export project information multiple times.

FineRuan has built a public cloud authentication server. You can initiate authorization requests by filling in authentication information, and send the requests to the public cloud authentication server for unified verification.

Functions

Public cloud registration has the following characteristics:

1. FineBI projects can be registered on public clouds, which are not limited by physical information. Changes in physical information will not cause registration failures.

2. Customers' FineBI servers must be connected to the authorization server through the public network. Customers who do not open the external network are not allowed to use public cloud registration.

The external network addresses that need to be opened include:

3. The registration is simple and easy to operate. There is basically no situation of registration failure.

4. You can apply for an authorization to register multiple projects. The price fluctuates according to the maximum registration capacity.

Public cloud can be registered on any FineBI server, which is flexible.

Obtaining an Authorization File

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

Business personnel will create an account and password for you after verifying the email, and email you the account information.

Note: If there are any special circumstances, indicate them in the email.

Verification and Registration

The admin logs into FineBI, and clicks Manage > Registration > Register Now.

Select Public Cloud in AUTH Method, enter the account and password in the email that business personnel have sent, and click Submit.

The effect of successful authentication is as follows:

Note: FineBI defaults to encrypting and storing public cloud passwords through RSA. If you switch encryption algorithms, the passwords will be updated synchronously.

Problem

If registration fails, a pop-up window will prompt:

Cause

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

Note: In addition to the above causes for failure, other errors will be reported uniformly: License file format is incorrect.

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

When you send business emails, the maximum registration capacity is specified.

1. When the number of servers does not exceed the maximum number that can be registered, the original server public cloud account can be used to register on the new server directly.

2. If the maximum registration capacity is exceeded, after the original server is unbound, the new server can be registered through the original server's public cloud account.

The admin logs into the decision-making platform and clicks Manage > Registration > Version Information > Re-register > Unbind to unbind the original server.

Note:

1. After the original server has been shut down for more than 24 hours, you can start registration for a new server, otherwise the original one  will still occupy the registration number.

2. If the original server is not unbound, when the new server registers with the original server's public cloud account, registration will fail, and the system will prompt: Max authorized number has been reached.