How to understand how SpringBoot generates a License

Preface

License refers to the copyright license. After we develop the system, if we don’t want users to use it for free all the time, for example, renewing based on time, the License will be useful.

We can specify the validity period of the License for the system and control the available time of the system.

So for the SpringBoot project, how to increase the License? Next, the prince will bring you a set of solutions. (Of course there is more than one way to implement it)

Generate License

The tool has been packaged, and friends can download and use it directly: https://gitee.com/lm970585581/spring-boot2-license

After downloading, open the cloud-license-serve project and start it directly.

Then call the project’s information acquisition interface: http://localhost:9081/license/getServerInfos?osName=windows

You will get results similar to the following, representing ip address, mac address, and cpu respectively. Serial number, motherboard serial number.

{
    "ipAddress": [
        "192.168.80.1",
        "192.168.220.1"
    ],
    "macAddress": [
        "01-51-56-C0-00-01",
        "00-52-56-C0-00-08",
        "BC-54-2D-DF-69-FC"
    ],
    "cpuSerial": "BFECFBFF000806EC",
    "mainBoardSerial": "L1HF16301D5"
}

Use the keytool tool that comes with JDK to generate the public and private key certificate store:

If we set the public key store password to: public_password1234 and the private key store password to: private_password1234, the generated command is as follows:

#生成命令
keytool -genkeypair -keysize 1024 -validity 3650 -alias "privateKey" -keystore "privateKeys.keystore" -storepass "public_password1234" -keypass "private_password1234" -dname "CN=localhost, OU=localhost, O=localhost, L=SH, ST=SH, C=CN"
 
#导出命令
keytool -exportcert -alias "privateKey" -keystore "privateKeys.keystore" -storepass "public_password1234" -file "certfile.cer"
 
#导入命令
keytool -import -alias "publicCert" -file "certfile.cer" -keystore "publicCerts.keystore" -storepass "public_password1234"

After the above command is executed, three files will be generated in the current path, namely: privateKeys.keystore, publicCerts.keystore, and certfile.cer. The file certfile.cer is no longer needed and can be deleted. The file privateKeys.keystore is used in the current ServerDemo project to generate license files for customers, while the file publicCerts.keystore is deployed to the customer server along with the application code. The user decrypts the license file and verifies its license. information.

Finally, we generate the license, and the calling interface address is: http://localhost:9081/license/generateLicense

The calling parameter is a json parameter with the following format:

{
    "subject": "license_demo",
    "privateAlias": "privateKey",
    "keyPass": "private_password1234",
    "storePass": "public_password1234",
    "licensePath": "C:/Users/zifangsky/Desktop/license_demo/license.lic",
    "privateKeysStorePath": "C:/Users/zifangsky/Desktop/license_demo/privateKeys.keystore",
    "issuedTime": "2018-07-10 00:00:01",
    "expiryTime": "2019-12-31 23:59:59",
    "consumerType": "User",
    "consumerAmount": 1,
    "description": "这是证书描述信息",
    "licenseCheckModel": {
        "ipAddress": ["192.168.245.1", "10.0.5.22"],
        "macAddress": ["00-50-56-C0-00-01", "50-7B-9D-F9-18-41"],
        "cpuSerial": "BFEBFBFF000406E3",
        "mainBoardSerial": "L1HF65E00X9"
    }
}

If the request is successful, a license.lic file will be generated at the path set by the licensePath parameter. This file is the server license file for deploying code to customers.

Using License

If you follow the above steps step by step, we have obtained the license.lic, and the next step is to use the license in our own projects .

cloud-license-client is an example of an imported project. You can open it and use it directly.

To introduce your own project, just import the following files into

# and configure the interceptor LicenseCheckInterceptor to use it. The configuration method is in the InterceptorConfig class, you can refer to it.

It should be noted here that using license requires two files: license.lic, publicCerts.keystore

The path configured in the demo project is an absolute path. Generally, we will configure a relative path and put the two Put the file under the project, and the configuration location is in the LicenseCheckListener class.

Just modify the following part to read it from a relative path.

I will not demonstrate how to do it here. Modified because it is easy to modify.

One more thing to note:

For the LicenseCheckModel and LicenseCreatorParam classes, after introducing them to your own client, you must ensure that the package name is consistent with the package name when generating the license, otherwise it will cause a sequence The problem of transformation failure.

The above is the detailed content of How to understand how SpringBoot generates a License. For more information, please follow other related articles on the PHP Chinese website!