Configuration software authorization management method and device
By generating and verifying a unique activation code based on hardware information and user registration information, the cumbersome issues of low-code configuration desktop tool activation and authorization management are solved, and project files are protected by encryption, improving the security and exclusiveness of project files.
Patent Information
- Application Number
- CN202411941106.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-26
- Publication Date
- 2025-06-13
AI Technical Summary
The existing low-code configuration desktop tools are cumbersome in activation and authorization management, and the lack of effective encryption protection for project files, resulting in reduced security.
By obtaining the hardware information of the device where the configuration software is located and combining it with the user registration information, a unique user activation code is generated, and the activation code is used to verify the hardware information of the current device to realize software authorization management. At the same time, a unique encryption identifier is generated to encrypt the project file to ensure the security of the file.
It realizes convenient authorization management of configuration software, meets permission control in multiple users or multiple devices, and ensures the security and exclusiveness of project files through encryption protection.
Smart Images
Figure CN120145339A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of software management, and particularly relates to a configuration software authorization management method and device. Background Art
[0002] Traditional software development models rely on a large amount of manual coding work, with long development cycles, high difficulty in requirement changes, and high technical requirements for developers. With the rapid development of information technology, low-code development platforms have become important tools for various enterprises and developers to improve software development efficiency. Among them, a low-code development platform (Low-Code Development Platform, LCDP) is a development platform that can quickly generate application programs without coding (zero code) or with a small amount of code, such as a low-code configuration desktop tool. Its method of developing application programs through visualization enables developers with different experience levels to create web pages and mobile application programs through a graphical user interface, using drag-and-drop components and model-driven logic.
[0003] Low-code development platforms enable non-technical personnel to quickly build applications through visualization programming and modular design, greatly shortening the development cycle. However, existing low-code configuration desktop tools generally have cumbersome activation and authorization management, and lack an effective encryption protection mechanism for engineering files. Among them, cumbersome activation and authorization management make it difficult for enterprises to conveniently control permissions in multi-user or multi-device usage scenarios. The lack of an effective encryption protection mechanism for engineering files easily leads to the leakage or unauthorized use of engineering files, greatly reducing the security of project engineering files. Summary of the Invention
[0004] In view of the technical problems existing in the prior art, the present invention provides a configuration software authorization management method and device to solve the technical problems that existing low-code configuration desktop tools generally have cumbersome activation and authorization management and lack an effective encryption protection mechanism for engineering files.
[0005] To achieve the above object, the technical solution adopted by the present invention is as follows: The present invention provides a configuration software authorization management method, including: Obtaining the hardware information of the device where the configuration software is located; Combining the hardware information of the device where the configuration software is located with the user registration information, and encrypting it with a public key to generate a user activation code; Obtaining the hardware information of the current device; Decrypting the user activation code with a private key to obtain the clear text of the activation code; verifying the hardware information of the current device with the clear text of the activation code; if the verification is successful, the configuration software is successfully authorized; If the configuration software is successfully licensed, a unique encryption identifier is generated for the project file of the newly created project, and the content of the project file of the newly created project is encrypted according to the unique encryption identifier; wherein, the unique encryption identifier is bound to the user activation code.
[0006] Further, the configuration software is a low-code configuration desktop tool.
[0007] Further, the hardware information of the device where the configuration software is located includes the hard disk serial number, MAC address, CPUID, and motherboard ID of the device where the configuration software is located; the hardware information of the current device includes the hard disk serial number, MAC address, CPUID, and motherboard ID of the current device.
[0008] Further, the process of combining the hardware information of the device where the configuration software is located with the user registration information and encrypting it with the public key to generate the user activation code is as follows: According to the rule of hardware information + user registration information, the hardware information of the device where the configuration software is located is combined with the user registration information and subjected to asymmetric encryption processing with the public key to generate the user activation code; wherein, the user registration information includes the user name, contact phone number, and user's affiliated region.
[0009] Further, the process of decrypting the user activation code with the private key to obtain the clear text of the activation code is as follows: Perform asymmetric decryption processing on the user activation code with the private key to obtain the clear text of the activation code.
[0010] Further, the process of verifying the hardware information of the current device with the clear text of the activation code is specifically as follows: Compare the hardware information of the device where the configuration software is located in the clear text of the activation code with the hardware information of the current device; If the comparison result of the hardware information is consistent, the verification is successful; otherwise, the verification fails.
[0011] Further, in the process of encrypting the content of the project file of the newly created project according to the unique encryption identifier, a symmetric encryption algorithm is used for encryption.
[0012] The present invention also provides a configuration software authorization management system, including: An activation code generation and verification module, which is used to obtain the hardware information of the device where the configuration software is located; combine the hardware information of the device where the configuration software is located with the user registration information and encrypt it with the public key to generate the user activation code; obtain the hardware information of the current device; decrypt the user activation code with the private key to obtain the clear text of the activation code; verify the hardware information of the current device with the clear text of the activation code; if the verification is successful, the configuration software is successfully licensed; An engineering file encryption module, which is used to generate a unique encryption identifier for the engineering file of a newly created project if the configuration software is successfully authorized, and encrypt the content of the engineering file of the newly created project according to the unique encryption identifier; wherein, the unique encryption identifier is bound to the user activation code.
[0013] The present invention also provides a configuration software authorization management device, including: A processor, suitable for executing a computer program; A computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by the processor, the configuration software authorization management method described above is executed.
[0014] The present invention also provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the configuration software authorization management method is implemented.
[0015] Compared with the prior art, the beneficial effects of the present invention are: The configuration software authorization management method provided by the present invention generates a unique user activation code through the hardware information of the device where the configuration software is located and the user registration information, ensuring the non-replicability and security of the user activation code; verifies the hardware information of the current device through the user activation code to implement the authorization management of the configuration software, meeting the permission control in multi-user or multi-device usage scenarios; secondly, encrypts the engineering file of the newly created project by using the unique encryption identifier bound to the user activation code, realizing the encryption protection of the project engineering file, and ensuring the security and exclusivity of the project file during transmission and storage.
[0016] The configuration software authorization management system, configuration software authorization management device and computer-readable storage medium provided by the present invention have all the advantages of the above configuration software authorization management method. Description of the Drawings
[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required to be used in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.
[0018] Figure 1 It is a flowchart of the configuration software authorization management method described in Embodiment 1; Figure 2 It is a structural block diagram of the configuration software authorization management system provided in Embodiment 2; Figure 3 Block diagram of the configuration software authorization management device provided for Embodiment 3. Detailed implementation manners
[0019] In order to make the technical problems, technical solutions and beneficial effects solved by the present application clearer and more understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application; obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.
[0020] Embodiment 1 As shown in the appended Figure 1 drawing, Embodiment 1 of the present application provides a configuration software authorization management method, including the following steps: Step 1: After the configuration software is installed, obtain the hardware information of the device where the configuration software is located. Among them, the configuration software is a low-code configuration desktop tool; the hardware information of the device where the configuration software is located includes the hard disk serial number, MAC address, CPU ID and motherboard ID of the device where the configuration software is located.
[0021] Step 2: Combine the hardware information of the device where the configuration software is located with the user registration information, and encrypt it with the public key to generate a user activation code.
[0022] Specifically, according to the rule of hardware information + user registration information, combine the hardware information of the device where the configuration software is located with the user registration information, and perform asymmetric encryption processing with the public key to generate a user activation code; among them, the user registration information includes the user name, contact phone number and the area to which the user belongs, and the RSA asymmetric encryption algorithm is used when performing asymmetric encryption processing with the public key.
[0023] It should be noted that the program code for generating the user activation code is specifically shown in Table 1 below.
[0024] Table 1 Program code for generating the user activation code
[0025] After combining the hardware information of the device where the configuration software is located with the user registration information to form a string, the process of performing asymmetric encryption processing with the public key to generate a user activation code is specifically as follows: convert the combined string into byte data; use the preset public key to encrypt the byte data to generate an encrypted ciphertext, and obtain the user activation code; among them, the preset public key is an RSA public key, and the RSA public key is stored in PEM or DER format.
[0026] Step 3: Obtain the hardware information of the current device. The hardware information of the current device includes the hard disk serial number, MAC address, CPUID, and motherboard ID of the current device.
[0027] Step 4: Decrypt the user activation code with the private key to obtain the cleartext activation code; use the cleartext activation code to verify the hardware information of the current device; if the verification is successful, the configuration software is successfully authorized. Among them, the RSA asymmetric encryption algorithm is used to decrypt the user activation code to obtain the cleartext activation code; the cleartext activation code contains the hardware information of the device where the configuration software is located and the user registration information.
[0028] Specifically, the process of using the cleartext activation code to verify the hardware information of the current device is as follows: Compare the hardware information of the device where the configuration software is located in the cleartext activation code with the hardware information of the current device; if the comparison result of the hardware information is consistent, the verification is successful; otherwise, the verification fails. Among them, if the hardware information verification is successful, the configuration software is successfully authorized, and the user can use the functions of the configuration software; if the verification fails, the configuration software authorization fails, the authorization is refused, and the user is prompted to contact support or reactivate.
[0029] It should be noted that the program code for verifying the activation code of the current device is specifically shown in Table 2 below.
[0030] Table 2 Program code for verifying the activation code of the current device
[0031] Step 5: If the configuration software is successfully authorized, generate a unique encryption identifier for the project file of the new project, and encrypt the content of the project file of the new project according to the unique encryption identifier. Among them, the unique encryption identifier is generated by using a random number generator, UUID, or combining the user activation code and the current timestamp information; preferably, the unique encryption identifier is bound to the user activation code, so that the unique encryption identifier and the user activation code are managed to ensure that the encryption identifier of each project file can be traced back to the specific user activation code.
[0032] In the process of encrypting the content of the project file of the new project according to the unique encryption identifier, a symmetric encryption algorithm is used for encryption; specifically, the unique encryption identifier is used as the encryption key; read the content of the project file and convert the read content of the project file into a byte stream; use the symmetric encryption algorithm and the encryption key to encrypt the byte stream to generate an encrypted project file.
[0033] It should be noted that the program code for encrypting the content of the engineering files of the new project is specifically shown in Table 3 below.
[0034] Table 3 Program code for encrypting the content of the engineering files of the new project
[0035] When it is necessary to open or edit the encrypted engineering file, the encrypted engineering file needs to be decrypted; among them, the process of decrypting the engineering file of the new project is specifically as follows: Obtain the unique encryption identifier associated with the engineering file of the new project, and use the obtained unique encryption identifier as the decryption key; read the encrypted engineering file; use the symmetric encryption algorithm and the decryption key to decrypt the encrypted content and restore the original engineering file content.
[0036] It should be noted that the program code for decrypting the content of the engineering files of the new project is specifically shown in Table 4 below.
[0037] Table 4 Program code for decrypting the content of the engineering files of the new project
[0038] In this Embodiment 1, by presetting a permission management module in the configuration software, the permissions of different user roles can be flexibly configured; among them, different user roles include developers, reviewers, and operators; when different user roles use the same project, their accessible content and executable operations are controlled according to their permissions; for example, developers can modify the project, reviewers can only view the project, and operators can only execute the deployed functions; preferably, the administrator assigns permissions to different users through a graphical interface to conveniently add or remove users, set permission levels, and view user operation records.
[0039] It should be noted that the program code for assigning permissions to different users through a graphical interface is specifically shown in Table 5 below.
[0040] Table 5 Program code for assigning permissions to different users through a graphical interface
[0041] In this Embodiment 1, an activation code invalidation and re-authorization mechanism is also provided; the activation code invalidation and re-authorization mechanism is specifically as follows: when the user replaces the device or needs to reactivate the software, the administrator invalidates the activation code of the old device through the background and generates a new activation code to bind to the new device; at the same time, it supports the authorization transfer function, allowing the user to transfer the user activation code to the new device without changing the hardware information of the device, preventing the need to repeatedly apply for an activation code when frequently updating the device.
[0042] For the configuration software license management method described in Embodiment 1, after the low-code configuration desktop tool is installed, the hardware information of the device where the low-code configuration desktop tool is located is read, and a user activation code is generated in combination with the user registration information. Among them, the activation code is generated by the server according to the hardware information of the device and the user registration information; the user activation code is encrypted using asymmetric encryption. After the user enters the activation code on the client, the client compares the activation code with the hardware information of the current device, and the software can be used normally after passing the verification. Among them, the user activation code is only bound to the device to prevent the activation code from being copied to other devices for use.
[0043] In Embodiment 1, whenever the user creates a new project, a unique encryption identifier is generated for the project file, and the content of the project file is encrypted using a symmetric encryption algorithm. When the user saves or exports the project file, the unique encryption identifier is bound to the user activation code to ensure that the project file can only be decrypted and used on the authorized device. After the project file is encrypted, even if the file is leaked, unauthorized users cannot access the file content.
[0044] Embodiment 2 As shown in the appendix Figure 2 As shown, Embodiment 2 provides a configuration software license management system, including an activation code generation and verification module and a project file encryption module.
[0045] The activation code generation and verification module is used to obtain the hardware information of the device where the configuration software is located; combine the hardware information of the device where the configuration software is located with the user registration information, and encrypt it with the public key to generate a user activation code; obtain the hardware information of the current device; decrypt the user activation code with the private key to obtain the activation code plaintext; use the activation code plaintext to verify the hardware information of the current device; if the verification is successful, the configuration software is successfully licensed.
[0046] The project file encryption module is used to, if the configuration software is successfully licensed, generate a unique encryption identifier for the project file of the new project, and encrypt the content of the project file of the new project according to the unique encryption identifier; among them, the unique encryption identifier is bound to the user activation code.
[0047] Embodiment 3 As shown in the appendix Figure 3 As shown, Embodiment 3 provides a configuration software license management device, including: a memory for storing a computer program; a processor for implementing the steps of the configuration software license management method when executing the computer program.
[0048] When the processor executes the computer program, it implements the steps of the above configuration software license management method. For example: Obtain the hardware information of the device where the configuration software is located; combine the hardware information of the device where the configuration software is located with the user registration information, and encrypt it with the public key to generate a user activation code; obtain the hardware information of the current device; decrypt the user activation code with the private key to obtain the clear text of the activation code; use the clear text of the activation code to verify the hardware information of the current device; if the verification is successful, the configuration software is successfully authorized; if the configuration software is successfully authorized, generate a unique encryption identifier for the project file of the new project, and encrypt the content of the project file of the new project according to the unique encryption identifier; wherein, the unique encryption identifier is bound to the user activation code.
[0049] Alternatively, when the processor executes the computer program, it implements the functions of each module in the above configuration software authorization management system. For example: The activation code generation and verification module is used to obtain the hardware information of the device where the configuration software is located; combine the hardware information of the device where the configuration software is located with the user registration information, and encrypt it with the public key to generate a user activation code; obtain the hardware information of the current device; decrypt the user activation code with the private key to obtain the clear text of the activation code; use the clear text of the activation code to verify the hardware information of the current device; if the verification is successful, the configuration software is successfully authorized. The project file encryption module is used to, if the configuration software is successfully authorized, generate a unique encryption identifier for the project file of the new project, and encrypt the content of the project file of the new project according to the unique encryption identifier; wherein, the unique encryption identifier is bound to the user activation code.
[0050] Exemplarily, the computer program can be divided into one or more modules / units, and the one or more modules / units are stored in the memory and executed by the processor to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of completing preset functions, and the instruction segments are used to describe the execution process of the computer program in the configuration software authorization management device.
[0051] For example, the computer program can be divided into an activation code generation and verification module and an engineering file encryption module. The specific functions of each module are as follows: The activation code generation and verification module is used to obtain the hardware information of the device where the configuration software is located; combine the hardware information of the device where the configuration software is located with the user registration information, and encrypt it with the public key to generate a user activation code; obtain the hardware information of the current device; decrypt the user activation code with the private key to obtain the clear text of the activation code; use the clear text of the activation code to verify the hardware information of the current device; if the verification is successful, the configuration software is successfully authorized. The engineering file encryption module is used to, if the configuration software is successfully authorized, generate a unique encryption identifier for the engineering file of the new project, and encrypt the content of the engineering file of the new project according to the unique encryption identifier; wherein, the unique encryption identifier is bound to the user activation code.
[0052] The configuration software authorization management device can be a computing device such as a desktop computer, a notebook, a palm computer, and a cloud server. The configuration software authorization management device may include, but is not limited to, a processor and a memory. Those skilled in the art can understand that the above are examples of the configuration software authorization management device, which do not constitute a limitation on the configuration software authorization management device, and may include more components than the above, or combine some components, or different components. For example, the configuration software authorization management device may also include input / output devices, network access devices, a bus, etc.
[0053] The so-called processor may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may also be any conventional processor, etc. The processor is the control center of the configuration software authorization management device, and connects various parts of the entire configuration software authorization management device through various interfaces and lines.
[0054] The memory can be used to store the computer program and / or module. The processor realizes various functions of the configuration software authorization management device by running or executing the computer program and / or module stored in the memory, and by calling the data stored in the memory.
[0055] The memory may mainly include a program storage area and a data storage area. Among them, the program storage area may store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.); the data storage area may store data created according to the use of the mobile phone (such as audio data, phone book, etc.). In addition, the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
[0056] Embodiment 4 Embodiment 4 of the present invention further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the steps of the configuration software authorization management method described above are implemented, for example: Obtain the hardware information of the device where the configuration software is located; combine the hardware information of the device where the configuration software is located with the user registration information, and encrypt it with a public key to generate a user activation code; obtain the hardware information of the current device; decrypt the user activation code with a private key to obtain the clear text of the activation code; use the clear text of the activation code to verify the hardware information of the current device; if the verification is successful, the configuration software is successfully authorized; if the configuration software is successfully authorized, generate a unique encryption identifier for the project file of the new project, and encrypt the content of the project file of the new project according to the unique encryption identifier; wherein, the unique encryption identifier is bound to the user activation code.
[0057] If the modules / units integrated in the configuration software authorization management system are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
[0058] Based on such an understanding, all or part of the processes in the configuration software authorization management method of the present invention can also be completed by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the configuration software authorization management method described above can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or preset intermediate form, etc.
[0059] The computer-readable storage medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, removable hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, software distribution medium, etc.
[0060] It should be noted that the content included in the computer-readable storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice within the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable storage medium does not include electrical carrier signals and telecommunication signals.
[0061] The configuration software authorization management method of the present invention authorizes the software through an activation code management system and encrypts and protects the project engineering files to ensure the security and exclusivity of the project; at the same time, it provides a multi-level user permission management function to ensure fine control of user permissions in different usage scenarios; specifically, it has strong security: based on hardware characteristics and encryption technology, a unique activation code is generated, and the uniqueness and non-replicability of the activation code are ensured through double verification, effectively preventing piracy; project file protection: the project files are encrypted through the AES encryption algorithm to ensure that even if the files are leaked, unauthorized users cannot read or modify the file content; flexible permission management: supports multi-level user permission allocation, and the administrator can flexibly allocate the permissions of different roles according to the specific project requirements. Activation code invalidation management: supports device migration and activation code re-authorization mechanisms to improve the user experience.
[0062] The above embodiments are only one of the implementation manners capable of implementing the technical solution of the present invention. The scope of protection required by the present invention is not limited only by this embodiment, but also includes any changes, substitutions and other implementation manners that are easily conceivable by any person skilled in the art within the technical scope disclosed by the present invention.
Claims
1. A configuration software authorization management method, characterized in that: include: Get the hardware information of the device where the configuration software is located; The hardware information of the device where the configuration software is located is combined with the user registration information, and encrypted with a public key to generate a user activation code; Get the hardware information of the current device; Decrypting the user activation code with a private key to obtain the activation code in plain text; Verifying the hardware information of the current device using the plain text of the activation code; If the verification is successful, the configuration software is authorized successfully; If the configuration software is authorized successfully, a unique encryption identifier is generated for the engineering file of the new project, and the content of the engineering file of the new project is encrypted according to the unique encryption identifier; wherein the unique encryption identifier is bound to the user activation code.
2. A configuration software authorization management method according to claim 1, characterized in that: The configuration software is a low-code configuration desktop tool.
3. A configuration software authorization management method according to claim 1, characterized in that: The hardware information of the device where the configuration software is located includes the hard disk serial number, MAC address, CPUID and motherboard ID of the device where the configuration software is located; the hardware information of the current device includes the hard disk serial number, MAC address, CPUID and motherboard ID of the current device.
4. A configuration software authorization management method according to claim 1, characterized in that: The process of combining the hardware information of the device where the configuration software is located with the user registration information and encrypting it with a public key to generate a user activation code is as follows: According to the rule of hardware information + user registration information, the hardware information of the device where the configuration software is located is combined with the user registration information, and asymmetric encryption is performed using a public key to generate a user activation code; wherein the user registration information includes a user name, a contact number, and a region to which the user belongs.
5. A configuration software authorization management method according to claim 1, characterized in that: The process of decrypting the user activation code with the private key to obtain the plain text of the activation code is as follows: The user activation code is asymmetrically decrypted using a private key to obtain a plain text activation code.
6. A configuration software authorization management method according to claim 1, characterized in that: The process of verifying the hardware information of the current device using the plain text of the activation code is specifically as follows: Compare the hardware information of the device where the configuration software is located in the activation code plain text with the hardware information of the current device; If the comparison result of the hardware information is consistent, the verification is successful; otherwise, the verification fails.
7. A configuration software authorization management method according to claim 1, characterized in that: In the process of encrypting the contents of the engineering file of the newly created project according to the unique encryption identifier, a symmetric encryption algorithm is used for encryption.
8. A configuration software authorization management system, characterized in that: include: The activation code generation and verification module is used to obtain the hardware information of the device where the configuration software is located; The hardware information of the device where the configuration software is located is combined with the user registration information, and encrypted with a public key to generate a user activation code; the hardware information of the current device is obtained; the user activation code is decrypted with a private key to obtain the activation code in plain text; The hardware information of the current device is verified using the plain text of the activation code; if the verification is successful, the configuration software is authorized successfully; The project file encryption module is used to generate a unique encryption identifier for the project file of the new project if the configuration software is authorized successfully, and encrypt the content of the project file of the new project according to the unique encryption identifier; wherein the unique encryption identifier is bound to the user activation code.
9. A configuration software authorization management device, characterized in that: include: a processor suitable for executing a computer program; A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by the processor, the configuration software authorization management method according to any one of claims 1 to 7 is executed.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the configuration software authorization management method as described in any one of claims 1 to 7 is implemented.