Creating a Security Key File

Version

Function Description

All changeable report configuration information is stored in the configuration database. The trial product uses a built-in HSQL database located at %BI_HOME%\webapps\webroot\WEB-INF\embed\finedb. In a formal environment, configuration information can be migrated to an external database, after which a db.properties file is generated in /WEB-INF/config to record information such as the address, username, and password of the configuration database.

This mainly applies to two aspects:

• Password encryption and decryption of the database in the db.properties file after migration

• Encryption and decryption of the data connection password, email password, FanRuan pass password (excluding the platform user password)

For higher key security, the logic of the root key is optimized.

During FineBI installation, select the Generate a security key file button. Three seed files are randomly generated after selection and read during project startup. Constant public and private keys are generated in the memory based on the seed. In this case, the generated seed files are used for encryption and decryption.

If you have high security requirements, select this button.

Note:

1. In Windows where the FineReport designer is installed in C:\Program Files without writing permissions, you can right-click the installation package and select Run as administrator if you want to generate a security key.

2. For details about how to configure external databases, refer to Configuring External Databases.

• If a new seed file is generated for encryption, use the new key for encryption.

• If a new seed file is generated for decryption, use the new key for decryption. If decryption fails, use the old key for re-decryption.

• Unless you manually place the seed files during JAR package upgrade, just use the old key for encryption and decryption.