Overview
Version
FineBI Version | Functional Change |
6.0 | / |
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:
Domain Name | Port | Description |
https://register.fanruan.com | 443 | Public cloud authentication server |
https://cloud.fanruan.com | 443 | Website management center |
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.
Procedures
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.
List | Requirement | Note | |
Priority contact | Contact FanRuan business personnel in advance to confirm relevant matters and sign the contract. | / | |
Sender | Use the email specified in the contract. | If you do not use the email specified in the contract to send registration information, the registration will fail. | |
Recipient | business@fanruan.com | / | |
Title | Official Authorization Document of {Company Name}'s Registration for FineBI | If you do not mark the company name in the email, the registration will fail. | |
Body | Basic information | Company name: {company name} Project name: {project name} Contract signing date: {YYYY-MM-DD} | / |
Registration method | Public cloud authentication | / | |
Maximum registration capacity | Maximum number of projects that can be registered. | If this option is not provided, it defaults to 1. | |
Account | Public cloud account name | If you need to specify a public cloud account name, indicate this in the email. If the account name has already been taken, it cannot be used. If you do not specify or specify an unavailable public cloud account name, business personnel will randomly create an account for you. | |
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.
Failed Registration
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.
Error Code | Error Name | Definition |
10000 | JSON_PARSER_ERROR | Incorrect data format |
10001 | PARAM_INPUT_ERROR | The entered parameteris incorrect. |
20000 | DO_NOT_NEED_DEACTIVATE | This machine is not authorized and does not need to be unbound. (If this prompt appears when you unbind, it means that this machine does not need to be unbound due to unauthorized access.) |
20001 | MYSQL_UPDATE_ERROR | Error occurs when you update MYSQL database. |
20002 | REDIS_UPDATE_ERROR | Error occurs when you insert data into REDIS database. |
30000 | LICENSE_EXPIRED | The certificate has expired. |
30001 | REPORT_VERSION_ERROR | Version mismatch |
30002 | ACCOUNT_STATUS_ERROR | Abnormal account status |
30003 | LICENSE_IP_ERROR | IP is not within the allowed range. |
30004 | LICENSE_DOMAIN_ERROR | The domain is not within the allowed range. |
30005 | LICENSE_APPNAME_ERROR | The app name is not within the allowed range. |
30006 | ACCOUNT_INPUT_ERROR | The account and password are not authorized. |
30007 | REGISTER_OUT_OF_LIMIT | The maximum number of authorizations has been reached. |
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.
Registration Migration
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.
