An authorization management method, device, system, equipment and computer storage medium

Abstract

This application discloses an authorization management method, apparatus, system, device, and computer storage medium. The method includes: an authorization slave node obtaining machine identity information of the server in the distributed system to which it belongs, and sending the machine identity information to a database; an authorization master node obtaining the machine identity information from the database, generating an authorization code based on the machine identity information, and sending the authorization code to the database; an authorization center obtaining the authorization code and generating an authorization file based on the authorization code, and sending it to the database; an authorization master node parsing the authorization file to obtain authorization information; and authorization slave nodes performing authorization operations on requests for commercial software usage rights from the server to which they belong, based on the authorization information. According to the embodiments of this application, unified authorization management of commercial software in a distributed system can be achieved.

Description

Technical Field

[0001] This application belongs to the field of information security technology, and in particular relates to an authorization management method, apparatus, system, device and computer storage medium. Background Technology

[0002] As governments and enterprises increase their level of informatization, the number of application systems is gradually growing. Among them, distributed software systems, by adopting a scalable system architecture and utilizing multiple devices to share the computing and storage load, improve the system's reliability, availability, and access efficiency.

[0003] Commercial software deployed in distributed systems generally has a limited lifespan, and distributed systems may also be resold. To protect the interests of commercial software providers, commercial software deployed in distributed systems requires authorization to operate.

[0004] How to license commercial software deployed in a distributed system is a problem that urgently needs to be solved in this field. Summary of the Invention

[0005] This application provides an authorization management method, apparatus, system, device, and computer storage medium, which can realize unified authorization management of commercial software in a distributed system.

[0006] In a first aspect, embodiments of this application provide an authorization management method applied to an authorization master node, the method comprising:

[0007] The machine identity information of the server in the distributed system is obtained from the database of the distributed system; the machine identity information is sent to the database by the authorized slave nodes deployed on the server.

[0008] Generate an authorization code based on the machine's identity information;

[0009] Send the authorization code to the database;

[0010] The authorization file is parsed to obtain authorization information;

[0011] The authorization information is saved to the database so that when the authorized slave node deployed on the server detects a commercial software usage permission request initiated by the server, it can retrieve the authorization information from the database and perform authorization operations on the commercial software usage permission request.

[0012] Secondly, embodiments of this application provide an authorization management device applied to an authorization master node, the device comprising:

[0013] The first acquisition module is used to acquire the machine identity information of the server in the distributed system from the database of the distributed system; the machine identity information is sent to the database by the authorized slave node deployed on the server;

[0014] The generation module is used to generate an authorization code based on the machine identity information;

[0015] The first sending module is used to send the authorization code to the database;

[0016] The first acquisition module is further configured to acquire an authorization file from the database, wherein the authorization file is generated by the authorization center based on the authorization code acquired from the database;

[0017] The parsing module is also used to parse the authorization file to obtain authorization information;

[0018] A storage module is used to save the authorization information to the database, so that when the authorization slave node deployed on the server detects a commercial software usage permission request initiated by the server, it can retrieve the authorization information from the database and perform authorization operations on the commercial software usage permission request.

[0019] Thirdly, this application also provides an authorization management method applied to an authorization slave node, wherein the authorization slave node is deployed on a server of a distributed system, the method comprising:

[0020] Obtain the machine identity information of the server to which the authorized slave node belongs;

[0021] The machine identity information is sent to the database of the distributed system so that the authorized master node can obtain the machine identity information from the database and generate an authorization code based on the machine identity information.

[0022] The authorization information is obtained from the database. The authorization information is generated by the authorization master node based on the authorization file. The authorization file is generated by the authorization center based on the authorization code generated by the authorization master node.

[0023] When a server initiates a request for permission to use commercial software, the authorization information is retrieved from the database, and the request for permission to use commercial software is authorized.

[0024] Fourthly, embodiments of this application also provide an authorization management device applied to an authorization slave node, wherein the authorization slave node is deployed on a server of a distributed system, and the device includes:

[0025] The second acquisition module is used to acquire the machine identity information of the server to which the authorized slave node belongs;

[0026] The second sending module is used to send the machine identity information to the database of the distributed system, so that the authorized master node can obtain the machine identity information from the database and generate an authorization code based on the machine identity information;

[0027] The second acquisition module is further configured to acquire authorization information from the database, wherein the authorization information is generated by the authorization master node based on the authorization file; and the authorization file is generated by the authorization center based on the authorization code generated by the authorization master node.

[0028] The authorization module is used to retrieve the authorization information from the database and perform authorization operations on the commercial software usage permission request when the server initiates a request for authorization.

[0029] Fifthly, embodiments of this application provide an authorization management system, the system comprising:

[0030] N authorized slave nodes, which are deployed on N servers in a distributed system, are used to execute any one of the authorization management methods provided in the embodiments of this application applied to the authorized slave nodes, where N is an integer greater than or equal to 1;

[0031] An authorized master node is deployed on a server in the distributed system other than the N servers to which the N authorized slave nodes belong, and is used to execute any of the authorization management methods provided in the embodiments of this application applied to the authorized master node;

[0032] A database, which is communicatively connected to the N authorized slave nodes and the authorized master node, is used to store data sent by the N authorized slave nodes and the authorized master node.

[0033] Sixthly, embodiments of this application provide an electronic device, the device comprising:

[0034] Processor and memory storing computer program instructions;

[0035] When the processor executes the computer program instructions, it implements the authorization management method described in either the first or third aspect of the embodiments of this application.

[0036] In a seventh aspect, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the authorization management method described in either the first or third aspect of embodiments of this application.

[0037] This application discloses an authorization management method, apparatus, system, device, and computer storage medium. It utilizes authorization slave nodes located on each server in a distributed system to collect machine identity information of each server. An authorization master node generates an authorization code corresponding to the machine identity information. An authorization center generates an authorization file based on the authorization code. The authorization master node parses the authorization file to obtain authorization information, enabling authorization slave nodes to authenticate and authorize commercial software usage permission requests based on the authorization information when a distributed system server initiates such requests. Through the collaborative work of the authorization master node and authorization slave nodes, this application obtains the identity identifier of the distributed system server and generates authorization information for commercial software on each server based on the identity identifier information. This further authorizes the commercial software in the distributed system based on the authorization information, achieving unified authorization management of commercial software in the distributed system. Attached Figure Description

[0038] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 This is a schematic diagram of the structure of an authorization management system provided in another embodiment of this application;

[0040] Figure 2 This is another schematic diagram of the structure of the authorization management system provided in yet another embodiment of this application;

[0041] Figure 3 This is a flowchart illustrating an embodiment of the authorization management method provided in this application;

[0042] Figure 4 This is a schematic diagram of the structure of an authorization management device provided in another embodiment of this application;

[0043] Figure 5 This is a schematic diagram of the structure of an authorization management method provided in another embodiment of this application;

[0044] Figure 6 This is a schematic diagram of the structure of an authorization management device provided in another embodiment of this application;

[0045] Figure 7 This is a schematic diagram of the structure of an electronic device provided in another embodiment of this application. Detailed Implementation

[0046] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0047] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0048] To address the problems in the prior art, embodiments of this application provide an authorization management method, apparatus, system, device, and computer storage medium.

[0049] Figure 1 A schematic diagram of the structure of an authorization management system provided in one embodiment of this application is shown. Figure 1 As shown, the authorization management system 100 provided in this application embodiment may include:

[0050] There are N authorized slave nodes 101, authorized master nodes 102, and database 103.

[0051] Figure 2 This application illustrates another structural diagram of an authorization management system provided in one embodiment, as shown below. Figure 2 As shown:

[0052] In some embodiments of this application, the authorization management system 100 may further include an authorization center 104.

[0053] The authorization management method provided in this application embodiment can be applied to the authorization management of commercial software in a distributed system, and the authorization management method provided in this application embodiment can be executed by the authorization management system 100 provided in this application embodiment.

[0054] The following describes an authorization management method provided by an embodiment of this application.

[0055] Figure 3 A flowchart illustrating an embodiment of an authorization management method provided in this application is shown. Figure 3 As shown in the embodiment of this application, an authorization management method is provided and applied to an authorization master node. The method may include:

[0056] Step 301: Obtain the machine identity information of the distributed system's servers from the distributed system's database; the machine identity information is sent to the database by the authorized slave nodes deployed on the server.

[0057] Step 302: Generate an authorization code based on the machine's identity information;

[0058] Step 303: Send the authorization code to the database;

[0059] Step 304: Obtain the authorization file from the database. The authorization file is generated by the authorization center based on the authorization code obtained from the database.

[0060] Step 305: Parse the license file to obtain license information;

[0061] Step 306: Save the authorization information to the database so that when the authorized slave node deployed on the server detects a commercial software usage permission request initiated by the server, it can retrieve the authorization information from the database and perform authorization operations on the commercial software usage permission request.

[0062] This application discloses an authorization management method applied to an authorization master node. It utilizes authorization slave nodes located on each server in a distributed system to collect machine identity information from each server. The authorization master node generates an authorization code corresponding to the machine identity information. An authorization center generates an authorization file based on the authorization code. The authorization master node parses the authorization file to obtain authorization information, enabling authorization slave nodes to authenticate and authorize commercial software usage permission requests based on the authorization information when a commercial software usage permission request is initiated by a distributed system server. Through the collaborative work of the authorization master node and authorization slave nodes, this application can obtain the identity identifier of the distributed system server and generate authorization information for commercial software on each server based on the identity identifier information. This further authorizes commercial software in the distributed system based on the authorization information, achieving unified authorization management of commercial software in the distributed system.

[0063] To better understand the call restriction method provided in this application, the following is combined with... Figure 1 The authorization management system 100 describes the call restriction method of the embodiments of this application:

[0064] In step 301, the authorized master node can obtain the machine identity information of the distributed system's servers from the distributed system's database; the machine identity information is sent to the database by the authorized slave nodes deployed on the servers.

[0065] In a distributed system, the machine identity information of each server serves as an identifier for that server or computer. This machine identity information can be collected by authorized slave nodes deployed on the corresponding servers. The authorized slave nodes can then encrypt the machine identity information and send it to the distributed system's database.

[0066] For example, when managing the authorization of commercial software in a distributed system, the authorization master node can obtain the machine identity information of each server in the distributed system from the database of the distributed system.

[0067] In embodiments of this application, machine identity information may include: the MAC address of the server on which the authorized slave node is deployed, CPU motherboard information, motherboard serial number, etc.

[0068] In step 302, the master node can generate an authorization code based on the machine identity information.

[0069] The authorization code can be verified by the authorization center to obtain the machine identity information in the authorization code and generate the corresponding authorization information.

[0070] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can generate an authorization code based on the machine identity information obtained from the database of the distributed system.

[0071] In embodiments of this application, before generating the authorization code based on the machine identity information, the following may also be included:

[0072] Retrieve heartbeat information from the distributed system's servers from the database. The heartbeat information is encrypted by authorized slave nodes deployed on the server and sent to the database using a data encryption algorithm. The heartbeat information may include the system time corresponding to when the heartbeat information was sent. Verify whether the system time corresponding to when the heartbeat information was sent and the current system time meet preset conditions.

[0073] Generating an authorization code based on machine identity information may include:

[0074] Under the condition that the preset conditions are met, an authorization code is generated based on the machine's identity information.

[0075] A heartbeat is a data packet containing time information sent between the authorized master node and the authorized slave node's server at regular intervals. The heartbeat information may include the system time at the time the heartbeat was sent.

[0076] Heartbeat information can be encrypted by authorized slave nodes deployed on the server and sent to the database of the distributed system along with the machine's identity information.

[0077] When the time information contained in the heartbeat packet meets the preset conditions, the authorized master node can generate an authorization code based on the machine identity information.

[0078] The preset conditions can be that the time information of sending the heartbeat packet is the same as the system's time information or that a preset threshold is met. The preset threshold can be a specified time range.

[0079] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can obtain the heartbeat information of the distributed system's servers from the distributed system's database. When the system time of sending the heartbeat information and the current time information meet preset conditions, the authorization master node generates an authorization code based on the machine identity information.

[0080] In this embodiment, the authorization master node verifies the heartbeat packet information sent to the database along with the machine identity information. When the time information contained in the heartbeat packet information meets the preset conditions, an authorization code is generated based on the machine identity information. This can prevent users from reusing the authorization code by modifying the machine time, thereby improving the reliability of authorization management.

[0081] In step 303, the authorizing master node can send its authorization code to the database.

[0082] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can send the generated authorization code to the database of the distributed system so that the authorization center of the authorization management system can obtain the authorization code from the database.

[0083] In embodiments of this application, sending an authorization code to the database may specifically include:

[0084] Send the authorization code to the database in the form of a QR code and / or an offline file.

[0085] The authorization code generated by the master node can be in the form of a QR code or an offline file.

[0086] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can save the authorization code in the database in the form of a QR code or an offline file.

[0087] In this embodiment, the authorization code generated by the master node can be saved to the database in the form of a QR code or an offline file. By saving the QR code as a QR code or an offline file, the authorization center of the authorization management system can obtain the authorization code from the database by scanning the QR code or obtaining the offline file, thereby realizing authorization management of the offline distributed system.

[0088] In embodiments of this application, before sending the authorization code to the database, the following may also be included:

[0089] The machine identity information in the authorization code is encrypted using AES to obtain the encrypted authorization code.

[0090] The authorization code includes: machine identity information and system identification code. The system identification code is a unique identifier generated by the authorization center for the distributed system.

[0091] The encrypted authorization code may include encrypted machine identity information and system identification code;

[0092] Sending an authorization code to the database can include:

[0093] Send the encrypted authorization code to the database.

[0094] The system identifier is a unique identifier generated by the authorization management system for the distributed system. This unique identifier can consist of numbers and / or letters, and the number of digits can be set by the deployment personnel of the authorization management system. The distributed system initializes this unique system identifier during deployment and runtime.

[0095] The authorization code contains the machine identity information of the server to which the authorized slave node belongs and the system's unique identifier. Each authorization code is bound to the corresponding machine identity information.

[0096] Before sending the authorization code to the database, the authorization master node can encrypt the authorization code using AES to obtain the encrypted authorization code.

[0097] The encrypted authorization code can consist of plaintext and ciphertext information. The ciphertext information is the encrypted information obtained by encrypting the machine identity information in the authorization code, and the plaintext information is the system identification code.

[0098] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can send an encrypted authorization code to the database to save the encrypted authorization code in the database.

[0099] In this embodiment, the master node stores the authorization code in the database of the distributed system after encryption, which prevents users of the distributed system without the decryption key from arbitrarily accessing the authorization code, thereby improving the reliability of authorization management.

[0100] In step 304, the master node can obtain the authorization file from the database. The authorization file is generated by the authorization center based on the authorization code obtained from the database.

[0101] In this embodiment of the application, the authorization file may store authorization information for user service information, wherein the user service information may include software or software functions.

[0102] The authorization file can be generated by the authorization center based on the authorization code containing machine identity information. The user service information in each authorization file corresponds to the service information of the server to which the machine identity information of each authorization code belongs.

[0103] After generating the authorization file, the authorization center can encrypt the authorization file and import it into the database of the distributed system.

[0104] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can obtain the authorization file from the database of the distributed system. The authorization file can be generated by the authorization center of the authorization management system based on the authorization code generated by the authorization master node.

[0105] In step 305, the master node can parse the authorization file to obtain authorization information.

[0106] The authorization information may include the identity information of the authorized machine and the authorization expiration time.

[0107] The authorization information contains permission information for system service requests. This permission information may include: the authorized object and the authorization expiration time. The authorized object can be determined based on the machine identity information in the authorization information.

[0108] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can parse the authorization file obtained in the above process to obtain authorization information that can be used to authorize the request for permission to use commercial software on the server.

[0109] In step 306, the master node can save the authorization information to the database so that when the slave nodes deployed on the server detect a commercial software usage permission request initiated by the server, they can retrieve the authorization information from the database and perform authorization operations on the commercial software usage permission request.

[0110] After parsing the authorization file and obtaining the authorization information, the master node can store the authorization information in the database of the distributed system.

[0111] When an authorized slave node deployed on the server detects a request for permission to use commercial software on the server, the authorized slave node can retrieve authorization information from the database to authenticate the request for permission to use commercial software based on the authorization information.

[0112] A request for permission to use commercial software can be a request to use the commercial software on the server, a request to use the full functionality of the commercial software, or a request to use other services or functions of the server.

[0113] If the authorization information contains permission information for a business request, the authorization slave node can authorize the commercial software usage permission request based on the permission information contained in the authorization information. The authorization operation may include determining the object to be authorized, the authorization time, and the authorization expiration time.

[0114] For example, when managing the authorization of commercial software in a distributed system, the master node of the authorization management system can send authorization information to the database of the distributed system, so that when the slave node detects a request for permission to use commercial software on the server, it can retrieve the authorization information from the database to authorize the request.

[0115] In embodiments of this application, before saving the authorization information to the database, the following may also be included:

[0116] Encrypt the authorization information using AES to obtain the encrypted authorization information;

[0117] Saving authorization information to the database can include:

[0118] Send encrypted authorization information to the database.

[0119] Before saving the authorization information to the database of the distributed system, the master node can encrypt the authorization information using AES.

[0120] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can encrypt the authorization information and store it in the database of the distributed system.

[0121] In this embodiment, the master node encrypts the authorization information and stores it in the database of the distributed system, thereby preventing users of the distributed system from arbitrarily using the authorization information and authorizing requests for access to commercial software on the server, thus improving the reliability of the authorization.

[0122] In embodiments of this application, AES encryption may include:

[0123] The system's identifier is parsed to obtain the AES encryption key and AES offset;

[0124] The object is encrypted using the AES encryption key and the AES offset.

[0125] AES is the Advanced Encryption Standard in cryptography. AES encryption is a symmetric encryption algorithm that uses the same key for both encryption and decryption. Symmetric encryption algorithms are very fast and suitable for applications that frequently send data.

[0126] The AES encryption key is used to encrypt data. In symmetric encryption algorithms, the encryption and decryption keys are the same.

[0127] The AES encryption process operates on a byte matrix, also known as the "state," with offsets representing the displacement of rows or columns within the byte matrix during the AES encryption process.

[0128] For example, when managing the authorization of commercial software in a distributed system, the authorization master node of the authorization management system can calculate the AES encryption key and the AES offset based on the system's identifier code, and then perform AES encryption on the encrypted object based on the AES encryption key and the offset.

[0129] In this embodiment, the authorization management method provided by this application uses AES encryption to encrypt the data in the authorization management process and uses the encrypted receipt for authorization management, thereby improving the reliability of authorization management.

[0130] according to Figure 3 The authorization management method shown in this application provides an authorization management device 400, which is applied to the authorization master node, such as... Figure 4 As shown, the device 400 may include:

[0131] The first acquisition module 401 can be used to obtain the machine identity information of the server in the distributed system from the database of the distributed system; the machine identity information is sent to the database by the authorized slave node deployed on the server;

[0132] The generation module 402 can be used to generate an authorization code based on the machine's identity information;

[0133] The first sending module 403 can be used to send authorization codes to the database;

[0134] The first acquisition module 401 can also be used to obtain an authorization file from the database. The authorization file is generated by the authorization center based on the authorization code obtained from the database.

[0135] The 404 parsing module can also be used to parse license files to obtain license information;

[0136] The storage module 405 can be used to save authorization information to the database, so that when the authorization slave node deployed on the server detects a commercial software usage permission request initiated by the server, it can retrieve the authorization information from the database and perform authorization operations on the commercial software usage permission request.

[0137] This application discloses an authorization management device applied to an authorization master node. It utilizes authorization slave nodes located on each server in a distributed system to collect machine identity information of each server. The authorization master node generates an authorization code corresponding to the machine identity information. An authorization center generates an authorization file based on the authorization code. The authorization master node parses the authorization file to obtain authorization information, enabling authorization slave nodes to authenticate and authorize commercial software usage permission requests based on the authorization information when a commercial software usage permission request is initiated by a distributed system server. Through the collaborative work of the authorization master node and authorization slave nodes, this application can obtain the identity identifier of the distributed system server and generate authorization information for commercial software on each server based on the identity identifier information. This further authorizes the commercial software in the distributed system based on the authorization information, achieving unified authorization management of commercial software in the distributed system.

[0138] In embodiments of this application, the authorization management device 400 may further include:

[0139] The encryption module can be used to encrypt the machine identity information in the authorization code using AES to obtain the encrypted authorization code;

[0140] The authorization code may include: machine identity information and system identification code. The system identification code is a unique identifier generated by the authorization center for the distributed system.

[0141] The encrypted authorization code may include encrypted machine identity information and system identification code;

[0142] The first sending module 403 can be specifically used to send an encrypted authorization code to the database.

[0143] In the implementation of this application, the encryption module can also be used to encrypt the authorization information with AES to obtain the encrypted authorization information;

[0144] The first sending module 403 can also be specifically used to send encrypted authorization information to the database.

[0145] In the embodiments of this application, the encryption module is specifically used to parse the system's identification code to obtain the AES encryption key and the AES offset;

[0146] The encryption module can also be specifically used to encrypt objects based on the AES encryption key and the AES offset.

[0147] In this embodiment of the application, the first acquisition module 401 can also be used to acquire heartbeat packet information of the server of the distributed system from the database;

[0148] The heartbeat information is encrypted by the authorized slave node deployed on the server according to the data encryption algorithm and sent to the database. The heartbeat information may include the system time corresponding to the time the heartbeat information is sent.

[0149] In embodiments of this application, the authorization management device 400 may further include:

[0150] The verification module can be used to verify whether the system time corresponding to the heartbeat packet sent and the current system time meet preset conditions;

[0151] The generation module 402 can be specifically used to generate an authorization code based on the machine identity information when preset conditions are met.

[0152] Machine identity information may include at least one of the following: MAC address, CPU motherboard information, and motherboard serial number.

[0153] Figure 5 A flowchart illustrating an authorization management method provided in an embodiment of this application is shown. Figure 5 As shown in the embodiment of this application, an authorization management method is provided and applied to an authorization slave node. The authorization slave node is deployed on a server of a distributed system. The method may include:

[0154] Step 501: Obtain the machine identity information of the server to which the authorized slave node belongs;

[0155] Step 502: Send machine identity information to the database of the distributed system so that the authorized master node can obtain the machine identity information from the database and generate an authorization code based on the machine identity information;

[0156] Step 503: Retrieve authorization information from the database. The authorization information is generated by the authorization master node based on the authorization file; the authorization file is generated by the authorization center based on the authorization code generated by the authorization master node.

[0157] Step 504: When a request for permission to use commercial software is detected by the server, the authorization information is retrieved from the database and the authorization operation is performed on the request for permission to use commercial software.

[0158] This application provides an authorization management method applied to authorization slave nodes. It utilizes authorization slave nodes located on various servers in a distributed system to collect machine identity information from each server. An authorization master node generates an authorization code corresponding to the machine identity information. An authorization center generates an authorization file based on the authorization code. The authorization master node parses the authorization file to obtain authorization information, enabling the authorization slave nodes to authenticate and authorize commercial software usage permission requests based on the authorization information when a commercial software usage permission request is initiated by a distributed system server. Through the collaborative work of the authorization master node and authorization slave nodes, this application can obtain the identity identifier of the distributed system server and generate authorization information for commercial software on each server based on the identity identifier information. This further enables the authorization of commercial software in the distributed system based on the authorization information, achieving unified authorization management of commercial software in the distributed system.

[0159] In step 501, the authorized slave node can obtain the machine identity information of the server to which the authorized slave node belongs.

[0160] Authorized slave nodes are deployed on various servers in a distributed system. During the authorization management process, authorized slave nodes can obtain the machine identity information of the server to which the authorized slave node belongs.

[0161] In embodiments of this application, machine identity information may include: the MAC address of the server on which the authorized slave node is deployed, CPU motherboard information, motherboard serial number, etc.

[0162] For example, when managing the authorization of commercial software in a distributed system, the authorized slave node can obtain the machine identity information of the server to which the authorized slave node belongs.

[0163] In step 502, the authorized master node can send machine identity information to the database of the distributed system so that the authorized master node can obtain the machine identity information from the database and generate an authorization code based on the machine identity information.

[0164] For example, when managing the authorization of commercial software in a distributed system, the authorization slave nodes of the authorization management system can obtain the machine identity information of the distributed system's servers and send it to the distributed system's database, so that the authorization master node can retrieve the machine identity information of the distributed system's servers from the database. The authorization master node can then generate a corresponding authorization code based on the machine identity information obtained from the database.

[0165] In step 503, the authorized slave node can obtain authorization information from the database. The authorization information is generated by the authorized master node based on the authorization file; the authorization file is generated by the authorization center based on the authorization code generated by the authorized master node.

[0166] The authorization information may include the identity information of the authorized machine and the authorization expiration time.

[0167] For example, when managing the authorization of commercial software in a distributed system, the authorization slave nodes of the authorization management system can obtain the authorization information parsed from the authorization master node based on the authorization file from the database. The authorization slave nodes can then manage the authorization permissions for the commercial software on the server to which they belong, based on the authorized machine identity information and authorization expiration time contained in the authorization information.

[0168] In step 504, the authorized slave node can retrieve authorization information from the database and perform authorization operations on the commercial software usage permission request when it detects that the server has initiated a request for commercial software usage permission.

[0169] If the authorization information contains permission information for a commercial software usage request, the authorization slave node can grant the commercial software usage permission request based on the permission information contained in the authorization information. The authorization operation may include determining the object to be authorized, the authorization time, and the authorization expiration time.

[0170] For example, when managing the authorization of commercial software in a distributed system, the authorization slave nodes of the authorization management system can obtain authorization information from the database of the distributed system. When a request for permission to use commercial software is detected on the server, the authorization slave node can authorize the request based on the authorization information.

[0171] In embodiments of this application, before sending machine identity information to the database of the distributed system, the following may also be included:

[0172] The machine identity information is encrypted using AES to obtain the encrypted machine identity information;

[0173] Sending machine identity information to a database in a distributed system can include:

[0174] Send encrypted machine identity information to the database.

[0175] Authorized slave nodes can encrypt machine identity information using AES before saving it to the distributed system's database.

[0176] For example, when managing the authorization of commercial software in a distributed system, the authorization slave nodes of the authorization management system can encrypt the machine identity information and store it in the database of the distributed system.

[0177] In this embodiment, the authorized slave node stores the machine information in the database of the distributed system after encryption, which prevents the machine identity information from being obtained and used by other unauthorized users, thus avoiding leakage of authorized data and improving the reliability of authorization.

[0178] according to Figure 5 The authorization management method shown in this application provides an authorization management device 600, which is applied to an authorization slave node. The authorization slave node is deployed on a server in a distributed system, such as... Figure 6 As shown, device 600 may include:

[0179] The second acquisition module 601 can be used to acquire the machine identity information of the server to which the authorized slave node belongs;

[0180] The second sending module 602 can be used to send machine identity information to the database of the distributed system so that the authorized master node can obtain the machine identity information from the database and generate an authorization code based on the machine identity information.

[0181] The second acquisition module 601 can also be used to retrieve authorization information from the database. The authorization information is generated by the authorization master node based on the authorization file; the authorization file is generated by the authorization center based on the authorization code generated by the authorization master node.

[0182] The authorization module 603 can be used to retrieve authorization information from the database and perform authorization operations on the commercial software usage permission request when a server initiates a request for commercial software usage permission.

[0183] This application discloses an authorization management device applied to authorization slave nodes. It utilizes authorization slave nodes located on various servers in a distributed system to collect machine identity information of each server. An authorization master node generates an authorization code corresponding to the machine identity information. An authorization center generates an authorization file based on the authorization code. The authorization master node parses the authorization file to obtain authorization information, enabling the authorization slave nodes to authenticate and authorize commercial software usage permission requests based on the authorization information when a distributed system server initiates such requests. Through the collaborative work of the authorization master node and authorization slave nodes, this application obtains the identity identifier of the distributed system server and generates authorization information for commercial software on each server based on the identity identifier information. This further authorizes the commercial software in the distributed system based on the authorization information, achieving unified authorization management of commercial software in the distributed system.

[0184] In embodiments of this application, the encryption module is further configured to perform AES encryption on the machine identity information to obtain the encrypted machine identity information;

[0185] The second sending module 602 can be specifically used to send encrypted machine identity information to the database.

[0186] according to Figure 1 The authorization management system 100 shown in this embodiment may include:

[0187] N authorized slave nodes 101 can obtain the machine identity information of the server to which the authorized slave node belongs;

[0188] Send machine identity information to the database of the distributed system so that the authorized master node can obtain the machine identity information from the database and generate an authorization code based on the machine identity information;

[0189] The authorization information is retrieved from the database. The authorization information is generated by the authorization master node based on the authorization file. The authorization file is generated by the authorization center based on the authorization code generated by the authorization master node.

[0190] When a request for permission to use commercial software is detected from the server, authorization information is retrieved from the database, and the request for permission to use commercial software is authorized.

[0191] In the embodiments of this application, the N authorized slave nodes 101 are functional modules of the authorized management system 100, and each authorized slave node can be in the form of a data packet or a code packet. Each server in the distributed system can connect with the authorized slave nodes by introducing the corresponding authorized slave node code packet.

[0192] N authorized slave nodes 101 can collect machine information of the servers associated with the current node, and can also intercept and authenticate requests for commercial software usage rights from the servers of the current node.

[0193] The authorized master node 102 can obtain the machine identity information of the distributed system's servers from the distributed system's database; the machine identity information is sent to the database by the authorized slave nodes deployed on the server.

[0194] Generate an authorization code based on the machine's identity information;

[0195] Send the authorization code to the database;

[0196] The authorization file is retrieved from the database. The authorization file is generated by the authorization center based on the authorization code retrieved from the database.

[0197] The license file is parsed to obtain the license information;

[0198] The authorization information is saved to the database so that when the authorization slave node deployed on the server detects a commercial software usage permission request initiated by the server, it can retrieve the authorization information from the database and perform authorization operations on the commercial software usage permission request.

[0199] The master node 102 is a functional module of the authorization management system 100. The master node 102 can be set on a computer in the distributed system that is independent of the server connected to the slave nodes. The master node 102 can be in the form of a data packet or a code packet, and can be connected to the computer in the form of a data packet or a code packet.

[0200] The master node 102 can generate authorization codes, update authorization codes, and verify authorization files to obtain authorization information.

[0201] Database 103 can communicate with N authorized slave nodes 101 and authorized master nodes 102 to store data sent by the N authorized slave nodes 101 and authorized master nodes 102.

[0202] Database 103 can be a database in a distributed system or a database that is set up independently.

[0203] Database 103 can be used as an intermediary for communication between authorized slave nodes and authorized master nodes. Database 103 can also store data from authorized master nodes or authorized slave nodes.

[0204] An authorization management system according to an embodiment of this application can collect machine identity information of each server in a distributed system using authorization slave nodes set up on each server. An authorization master node generates an authorization code corresponding to the machine identity information. The authorization center generates an authorization file based on the authorization code, and the authorization master node parses the authorization file to obtain authorization information. This allows authorization slave nodes to authenticate and authorize commercial software usage permission requests based on the authorization information when a distributed system server initiates such requests. Through the collaborative work of the authorization master node and authorization slave nodes, this application can obtain the identity identifier of the distributed system server and generate authorization information for commercial software on each server based on the identity identifier information. This further enables the authorization of commercial software in the distributed system based on the authorization information, achieving unified authorization management of commercial software in the distributed system.

[0205] In some embodiments of this application, according to Figure 2 As shown, the authorization management system 100 may also include: an authorization center 104.

[0206] The authorization center can be set up by the system provider and can be used to retrieve authorization codes from the database by scanning authorization QR codes and / or obtaining offline files, and generate authorization files based on the authorization codes;

[0207] Authorization Center 104 can also be used to import authorization files into a database.

[0208] In the embodiments of this application, the authorization center 104 is a functional module of the authorization management system 100, and can be set by the system provider. The authorization center 104 can be used to obtain the authorization code generated by the authorization master node, generate an authorization file based on the authorization code, and import the authorization file into the database.

[0209] In this embodiment, the authorization center can obtain the authorization code generated by the authorization master node of the authorization management system by scanning a QR code and / or importing offline files, without the need for network transmission. This enables software authorization management of the offline distributed system and improves the adaptability of the authorization management system.

[0210] Figure 7 A schematic diagram of the hardware structure of the electronic device 700 provided in an embodiment of this application is shown.

[0211] The electronic device 700 may include a processor 701 and a memory 702 storing computer program instructions.

[0212] Specifically, the processor 701 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0213] Memory 702 may include mass storage for data or instructions. For example, and not limitingly, memory 702 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 702 may include removable or non-removable (or fixed) media. Where appropriate, memory 702 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 702 is non-volatile solid-state memory.

[0214] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, generally, memory may include one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the methods according to the first and third aspects of this application.

[0215] The processor 701 implements any of the authorization management methods described in the above embodiments by reading and executing computer program instructions stored in the memory 702.

[0216] In one example, the electronic device 700 may also include a communication interface 703 and a bus 710. Wherein, as... Figure 7 As shown, the processor 701, memory 702, and communication interface 703 are connected through bus 710 and complete communication with each other.

[0217] The communication interface 703 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0218] Bus 710 may include hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 710 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0219] The electronic device 700 can execute the authorization management method in the embodiments of this application, thereby achieving the combination Figure 3 , Figure 5 The described authorization management methods and Figure 4 , Figure 6 And the described authorization management device.

[0220] Furthermore, in conjunction with the authorization management methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the authorization management methods in the above embodiments.

[0221] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0222] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. The programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0223] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0224] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0225] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. An authorization management method characterized by, The method is applied to an authorized master node, and comprises the following steps: Obtaining machine identity information of a server of a distributed system from a database of the distributed system; the machine identity information is sent to the database by an authorized slave node deployed on the server; Obtaining heartbeat packet information of the server of the distributed system from the database; the heartbeat packet information is encrypted according to a data encryption algorithm and then sent to the database by the authorized slave node deployed on the server, and the heartbeat packet information comprises system time corresponding to the sending of the heartbeat packet information; Checking whether the system time corresponding to the sending of the heartbeat packet information and current system time satisfy a preset condition; Generating an authorization code according to the machine identity information in the case of satisfying the preset condition; Sending the authorization code to the database; Obtaining an authorization file from the database, wherein the authorization file is generated by an authorization center according to the authorization code obtained from the database; Analyzing the authorization file to obtain authorization information; Saving the authorization information into the database, so that the authorized slave node deployed on the server obtains the authorization information from the database when detecting a server-initiated commercial software use permission request, and performs an authorization operation on the commercial software use permission request.

2. The method of claim 1, wherein, Before the sending of the authorization code to the database, the method further comprises the following steps: AES-encrypting the machine identity information in the authorization code to obtain an encrypted authorization code; The authorization code comprises the machine identity information and an identification code of the system, wherein the identification code of the system is a unique identification code of the distributed system generated by the authorization center; The encrypted authorization code comprises encrypted machine identity information and the identification code of the system; The sending of the authorization code to the database comprises the following steps: Sending the encrypted authorization code to the database.

3. The method of claim 1, wherein, Before the saving of the authorization information into the database, the method further comprises the following steps: AES-encrypting the authorization information to obtain encrypted authorization information; The saving of the authorization information into the database comprises the following steps: Sending the encrypted authorization information to the database.

4. The method according to any one of claims 2 and 3, characterized in that, The AES encryption comprises the following steps: Analyzing the identification code of the system to obtain an AES encryption key and an AES offset; Encrypting an encryption object according to the AES encryption key and the AES offset.

5. The method of claim 1, wherein, The machine identity information comprises at least one of the following: a MAC address, CPU mainboard information, and a mainboard serial number.

6. The method of claim 1, wherein, The sending of the authorization code to the database comprises the following steps: Sending the authorization code to the database in the form of a two-dimensional code and / or an offline file.

7. An authorization management apparatus characterized by comprising: The device is applied to an authorized master node, and comprises the following steps: A first obtaining module is configured to obtain machine identity information of a server of a distributed system from a database of the distributed system; the machine identity information is sent to the database by an authorized slave node deployed on the server; A second obtaining module is configured to obtain heartbeat packet information of the server of the distributed system from the database; the heartbeat packet information is encrypted according to a data encryption algorithm and then sent to the database by the authorized slave node deployed on the server, and the heartbeat packet information comprises system time corresponding to the sending of the heartbeat packet information; The first obtaining module is further configured to obtain heartbeat packet information of a server of a distributed system from the database; the heartbeat packet information is sent to the database by an authorized slave node deployed on the server after being encrypted according to a data encryption algorithm, and the heartbeat packet information comprises system time corresponding to a time when the heartbeat packet information is sent; The checking module is configured to check whether the system time corresponding to the time when the heartbeat packet is sent and a current system time satisfy a preset condition; The generating module is configured to generate an authorization code according to the machine identity information in a case where the preset condition is satisfied; The first sending module is configured to send the authorization code to the database; The first obtaining module is further configured to obtain an authorization file from the database, wherein the authorization file is generated by an authorization center according to the authorization code obtained from the database; The analyzing module is further configured to analyze the authorization file to obtain authorization information, wherein the authorization information comprises authorized machine identity information and authorization expiration time; The saving module is configured to save the authorization information into the database, so that the authorized slave node deployed on the server obtains the authorization information from the database when detecting a business software usage permission request initiated by the server, and performs an authorization operation on the business software usage permission request.

8. An authorization management method characterized by, The method applied to an authorized slave node deployed on a server of a distributed system, and the method comprises: obtaining machine identity information and heartbeat packet information of a server to which the authorized slave node belongs; the heartbeat packet information is obtained by the authorized slave node according to a data encryption algorithm, and the heartbeat packet information comprises system time corresponding to a time when the heartbeat packet information is sent; sending the machine identity information and the heartbeat packet information to a database of the distributed system, so that an authorized master node obtains the machine identity information and the heartbeat packet information from the database, and generates an authorization code according to the machine identity information in a case where system time corresponding to the time when the heartbeat packet is sent and a current system time satisfy a preset condition; obtaining authorization information from the database, wherein the authorization information is generated by the authorized master node according to an authorization file; the authorization file is generated by an authorization center according to an authorization code generated by the authorized master node; when detecting a business software usage permission request initiated by the server, obtaining the authorization information from the database, and performing an authorization operation on the business software usage permission request.

9. The method of claim 8, wherein, Before the machine identity information is sent to the database of the distributed system, the method further comprises: performing AES encryption on the machine identity information to obtain encrypted machine identity information; the machine identity information is sent to the database of the distributed system, comprising: sending the encrypted machine identity information to the database.

10. An authorization management apparatus characterized by comprising: The device applied to an authorized slave node deployed on a server of a distributed system, and the device comprises: The second obtaining module is configured to obtain machine identity information and heartbeat packet information of a server to which the authorized slave node belongs; the heartbeat packet information is obtained by encrypting the data encryption algorithm by the authorized slave node, and the heartbeat packet information comprises a system time corresponding to the sending of the heartbeat packet information; The second sending module is configured to send the machine identity information and the heartbeat packet information to a database of the distributed system, so that the authorized master node obtains the machine identity information and the heartbeat packet information from the database, and generates an authorization code according to the machine identity information when the system time corresponding to the sending of the heartbeat packet information and the current system time satisfy a preset condition; The second obtaining module is further configured to obtain authorization information from the database, wherein the authorization information is generated by the authorized master node according to an authorization file; and the authorization file is generated by the authorization center according to the authorization code generated by the authorized master node; The authorization module is configured to obtain the authorization information from the database when detecting that the server initiates a commercial software usage permission request, and perform an authorization operation on the commercial software usage permission request.

11. An authorization management system, characterized by The system comprises: N authorized slave nodes, wherein N is an integer greater than or equal to 1, the N authorized slave nodes are deployed on N servers of the distributed system, and are configured to execute the authorization management method of any one of claims 8-9; An authorized master node, wherein the authorized master node is deployed on a server of the distributed system other than the N servers to which the N authorized slave nodes belong, and is configured to execute the authorization management method of any one of claims 1-6; A database, wherein the database is in communication connection with the N authorized slave nodes and the authorized master node, and is configured to store data sent by the N authorized slave nodes and the authorized master node.

12. The system of claim 11, wherein, The system further comprises: An authorization center, wherein the authorization center is arranged at a system provider, and is configured to obtain an authorization code from the database by scanning an authorization two-dimensional code and / or obtaining an offline file, and generate an authorization file according to the authorization code; The authorization center is further configured to import the authorization file into the database.

13. An electronic device, comprising: The device comprises a processor and a memory storing computer program instructions; The processor executes the computer program instructions to implement the authorization management method of any one of claims 1-6 and / or claims 8-9.

14. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the authorization management method of any one of claims 1-6 and / or claims 8-9.

15. A computer program product, characterised in that, The instructions in the computer program product are executed by the processor of the electronic device, so that the electronic device executes the authorization management method of any one of claims 1-6 and / or claims 8-9.

Images