I. Overview
1. Version
| Designer | JAR | Funtion change |
|---|---|---|
| 10.0 | - | - |
| 10.0.17 | - | Public Cloud AUTH is not limited by physical information |
| 10.0.19 | - | Encrypted storage of public cloud account passwords |
2. Application scenario
Users need to register multiple projects, it is very troublesome to export project information for many times, and they do not want to set up an authorization server locally.
Fansoft builds a public cloud authentication server. Customers initiate authorization requests by filling in authentication information and send them to the public cloud authentication server for unified authentication and authorization.
3. Function introduction
Public Cloud AUTH has the following characteristics:
1) Public Cloud AUTH for report projects of 10.0.17 and later versions will not be limited by physical information, and the change of physical information will not lead to registration failure.
Version earlier than 10.0.17 require fixed physical information for Public Cloud AUTH. If the physical information changes, the registration becomes invalid. If the registration fails, please refer to Section II.4 to unbind and re-register.
2) The client report server must be connected to the authorization server through the public network. The client who is not allowed to open the external network cannot use this registration method.
The following extranet addresses need to be opened:
| Domain name | Port | Description |
|---|---|---|
| https://register.fanruan.com | 443 | Public Cloud AUTH Server |
| https://cloud.fanruan.com | 443 | Address Management Center |
3) The registration method is simple and easy to operate, and basically there will be no registration failure.
4) When users apply for one authorization, they can register multiple projects, and the price fluctuates according to the "maximum number of registrable projects".
If the IP address of the report server is not limited, the report server can be registered on any report server.
II. Instructions
1. Obtain authorization file
Please use the email address specified in the contract to send the registration information to business@fanruan.com in the following format:
After receiving an email, the business generates an account and password for the user and sends the email to the user.
| List | Requirement | Note | |
|---|---|---|---|
| First contact | Please contact FanRuan sales in advance to confirm relevant matters and sign the contract | - | |
| Sender | Please use the email address specified in the contract | If the email from which the registration information is sent is not specified in the contract, the registration will not be granted. | |
| Recipient | business@fanruan.com | - | |
| Tiltle | XXX company registered FineReport official authorization document | If the company name is not indicated when sending the registration information, it will not be registered. | |
| Text | Basic information | Company name: XXX Company Project name: XXX Project Contract signing date: XX, XX, XXXX | - |
| Register mode | Public Cloud AUTH | - | |
| Maximum number of registrations | The number of projects allowed to register | If this option is not provided, the default value is 1. | |
| Report server IP | Restrict which report server IP addresses are allowed to be registered Format: 192.168.100.25-192.168.100.26, 192.168.0.1 | If this option is not provided, this restriction is not required | |
| Account | Public cloud account name | If you need to specify a public cloud account name, specify it in the email. If the account name is already occupied, it cannot be used. If you specify unavailable public cloud account name or not, the business will randomly generate an account for you. | |
2. Complete the registration
Login the decision-making system as an administrator, click Manage -> Registration -> Sign Up Now.
Select Public Cloud AUTH and enter the account and password. Then, click on Submit Authentication to complete the registration process.
Note: The JAR package in 2021-10-14 and later projects uses RSA to encrypt and store public cloud passwords by default. If the encryption algorithm is switched, the password will be updated synchronously.
A success message will be displayed, along with registered information including "Maximum number of registration".
III. Registration failed
1. Phenomenon description
If the registration fails, a pop-up window will appear on the page, as shown in the figure below:
2. Reasons for failure
Click on the detailed information to view the reason for the registration failure, and perform troubleshooting based on the specific failure reason.
| Error code | Wrong name | Meaning |
|---|---|---|
| 10000 | JSON_PARSER_ERROR | The data format is incorrect. |
| 10001 | PARAM_INPUT_ERROR | The parameter you entered is incorrect. |
| 20000 | DO_NOT_NEED_DEACTIVATE | The machine is not authorized and does not need to be unbound (this prompt appears when unbinding, indicating that this machine does not need to be unbound because it is not authorized). |
| 20001 | MYSQL_UPDATE_ERROR | Error updating MYSQL database |
| 20002 | REDIS_UPDATE_ERROR | Error inserting data into REDIS database |
| 30000 | LICENSE_EXPIRED | Certificate has expired |
| 30001 | REPORT_VERSION_ERROR | Version does not match |
| 30002 | ACCOUNT_STATUS_ERROR | The account status is abnormal |
| 30003 | LICENSE_IP_ERROR IP | It is not in the allowed range |
| 30004 | LICENSE_DOMAIN_ERROR | The domain name is not within the allowed range |
| 30005 | LICENSE_APPNAME_ERROR | The application name is not within the allowed range |
| 30006 | ACCOUNT_INPUT_ERROR | The account and password are not authorized |
| 30007 | REGISTER_OUT_OF_LIMIT | It has reached the maximum number of authorizations |
Note: In addition to the failure reasons other than the above, other unified error: the content of the certificate is incorrect.
When there are multiple failure reasons, they will all be displayed in the platform.
IV. Registration migration
When sending business emails, the maximum number of registrations is indicated.
1) When the number of servers does not exceed the maximum number of registrations, you can directly use the original server's public cloud account to register on the new server.
2) If the maximum number of registrations is exceeded, after the original server is unbound, the new server uses the original server's public cloud account to register.
The administrator logs in to the decision-making platform, clicks Manage>Registration>Version Information, and clicks Re-register>Unbind to unbind the old server. As shown below:
Note 1: The registration of the new server can only be performed after the original server is shut down for more than 24 hours, otherwise the number of registrations will still be occupied.
Note 2: If the original server does not unbind, when the new server uses the original server's public cloud account to register, the registration fails, and the prompt: the maximum number of authorizations has been reached.
