Software authority management method, device and equipment

Abstract

The invention relates to the technical field of authority management, and discloses a software authority management method, device and equipment, and the method comprises the steps: obtaining token information of a current operation account in response to a target operation of the current operation account on target software; generating an operation request instruction based on the token information and the operation type of the target operation, and sending the operation request instruction to a server; the server is used for performing permission verification on the target operation based on the operation request instruction and returning a permission verification result to the client; and obtaining a permission verification result sent by the server, and executing an authorization action corresponding to the permission verification result on the target operation. According to the method, the server side performs permission verification on the target operation based on the operation request instruction, so that the client side executes the authorization action corresponding to the permission verification result on the target operation, identity authentication and authorization management are performed before the software is operated, and the security and reliability of software management are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of rights management, and in particular to a software rights management method, device and equipment. Background Art

[0002] In Linux systems, Yum (Yellowdog Updater Modified) is a commonly used software package management tool that helps users install, update, and uninstall software packages. However, in the absence of effective identity authentication and authorization management, unauthorized users may use Yum to perform illegal operations, such as installing malware or stealing sensitive information, resulting in security risks in the current software management. Summary of the invention

[0003] In view of this, the present invention provides a software rights management method, apparatus and device to solve the problem of potential security risks in current software management.

[0004] In a first aspect, the present invention provides a software rights management method, which is applied to a client, and the method comprises:

[0005] In response to the target operation of the current operating account on the target software, acquiring token information of the current operating account;

[0006] Based on the token information and the operation type of the target operation, an operation request instruction is generated, and the operation request instruction is sent to the server; the server is used to perform permission verification on the target operation based on the operation request instruction, and return the permission verification result to the client;

[0007] Get the permission verification result sent by the server, and perform the authorization action corresponding to the permission verification result on the target operation.

[0008] In an optional implementation, performing an authorization action corresponding to a permission verification result on a target operation includes:

[0009] If the permission verification result is authorization successful, the target operation of the target software by the current operating account is executed;

[0010] If the permission check result is authorization failure, the target operation of the current operating account on the target software will not be performed.

[0011] In a second aspect, the present invention provides a software rights management method, which is applied to a server, and the method comprises:

[0012] In response to the operation request instruction sent by the client, the operation request instruction is parsed to obtain token information and the operation type of the target operation;

[0013] Deserialize the token information to obtain the current operating account, and perform account verification on the current operating account based on the account information of the current operating account;

[0014] If the account verification of the current operating account passes, then based on the permission information of the current operating account, the operation type of the target operation is verified, the permission verification result is obtained, and the permission verification result is returned to the client.

[0015] In an optional implementation, based on the account information of the current operating account, the current operating account is verified, including:

[0016] Get the account status corresponding to the current operating account;

[0017] If the account status is the first status, it is determined that the account verification of the current operating account has passed;

[0018] If the account status is the second status, it is determined that the account verification of the current operating account has failed.

[0019] In an optional implementation, based on the account information of the current operating account, the current operating account is verified, including:

[0020] Get the account token corresponding to the current operating account;

[0021] If the token information is consistent with the account token, it is determined that the account verification of the current operating account has passed;

[0022] If the token information is inconsistent with the account token, it is determined that the account verification of the current operating account has failed.

[0023] In an optional implementation, based on the permission information corresponding to the token information, the operation type of the target operation is subjected to permission verification to obtain a permission verification result, including:

[0024] Compare the permission information with the operation type;

[0025] If the permission information contains the permission corresponding to the operation type, the permission verification result is determined to be authorization success;

[0026] If the permission information does not include the permission corresponding to the operation type, the permission verification result is determined to be authorization failure.

[0027] In an optional embodiment, the method further includes:

[0028] Initialize the administrator account and configure the token information of the administrator account; the administrator account is used to create a first operation account in the client and save the token information of the first operation account;

[0029] In response to the account creation request output by the administrator account, the account information and permission information of the first operating account are acquired and saved.

[0030] In a third aspect, the present invention provides a software rights management device, which is applied to a client, and the device includes:

[0031] A token acquisition module, used to acquire token information of the current operating account in response to the target operation of the current operating account on the target software;

[0032] The instruction generation module is used to generate an operation request instruction based on the token information and the operation type of the target operation, and send the operation request instruction to the server; the server is used to perform permission verification on the target operation based on the operation request instruction, and return the permission verification result to the client;

[0033] The action execution module is used to obtain the permission verification result sent by the server and execute the authorization action corresponding to the permission verification result on the target operation.

[0034] In a fourth aspect, the present invention provides a software rights management device, which is applied to a server, and the device includes:

[0035] The instruction parsing module is used to respond to the operation request instruction sent by the client, parse the operation request instruction, and obtain the token information and the operation type of the target operation;

[0036] The account verification module is used to deserialize the token information, obtain the current operating account, and perform account verification on the current operating account based on the account information of the current operating account;

[0037] The permission verification module is used to perform permission verification on the operation type of the target operation based on the permission information of the current operation account if the account verification of the current operation account passes, obtain the permission verification result, and return the permission verification result to the client.

[0038] In a fifth aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the software permission management method of the first aspect, the second aspect or any corresponding embodiment thereof by executing the computer instructions.

[0039] In a sixth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the software permission management method of the first aspect, the second aspect or any corresponding embodiment thereof.

[0040] In a seventh aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the software rights management method of the first aspect, the second aspect or any corresponding embodiment thereof.

[0041] The software permission management method provided by the embodiment of the present invention generates an operation request instruction based on the token information of the current operation account and the operation type of the target operation, performs permission verification on the target operation based on the operation request instruction through the server, and returns the permission verification result to the client, so that the client executes the authorization action corresponding to the permission verification result on the target operation, thereby performing identity authentication and authorization management before operating the software, thereby improving the security and reliability of software management. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0043] Figure 1 is a flowchart of a software rights management method according to an embodiment of the present invention;

[0044] Figure 2 is a flowchart of a software rights management method according to an embodiment of the present invention;

[0045] Figure 3 is a flowchart of a specific implementation of the software rights management method according to an embodiment of the present invention;

[0046] Figure 4 is a structural block diagram of a software rights management device according to an embodiment of the present invention;

[0047] Figure 5 is a structural block diagram of a software rights management device according to an embodiment of the present invention;

[0048] Figure 6 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0050] In Linux systems, Yum (Yellowdog Updater Modified) is a commonly used software package management tool that helps users install, update, and uninstall software packages. However, in the absence of effective identity authentication and authorization management, unauthorized users may use Yum to perform illegal operations, such as installing malware or stealing sensitive information, resulting in security risks in the current software management.

[0051] Based on this, an embodiment of the present invention provides a software permission management method, which generates an operation request instruction based on the token information of the current operation account and the operation type of the target operation, and performs permission verification on the target operation based on the operation request instruction through the server, and returns the permission verification result to the client, so that the client executes the authorization action corresponding to the permission verification result on the target operation, thereby performing identity authentication and authorization management before operating the software, thereby improving the security and reliability of software management.

[0052] According to an embodiment of the present invention, a software rights management method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0053] On the one hand, in this embodiment, a software rights management method is provided, which can be used in a client, namely, AuthYum. Figure 1 is a flowchart of a software rights management method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0054] Step S101 , in response to a target operation of a current operating account on a target software, acquiring token information of the current operating account.

[0055] In the embodiment of the present invention, in response to the target operation of the current operating account on the target software in the AuthYum client, the token information of the current operating account is first obtained from the token information of multiple operating accounts stored locally in the client.

[0056] In an optional implementation, the token information of the operation account may be stored in the / etc / yum.conf file, which serves as a global configuration file of the AuthYum client and defines the global behavior of AuthYum.

[0057] In an optional implementation, multiple software can be managed simultaneously through the AuthYum client, and the token information of the operating accounts involved in the multiple software can be stored in the / etc / yum.conf file to avoid duplicate storage of information and facilitate calling the corresponding token information when performing permission verification on the target operation of the current operating account.

[0058] In an optional implementation, when managing multiple software at the same time through the AuthYum client, the operation account related to each software can be stored separately, so as to achieve refined management. For example, the token information of the operation account can be stored in the configuration file of the corresponding software, such as in the .repo file of the corresponding software in the / etc / yum.repos.d / directory. When the target operation of the current operation account on the target software is detected, the token information of the current operation account is obtained from the configuration file of the target software. If the token information of the current operation account is not obtained, it indicates that the current operation account does not have the operation authority for the target software. At this time, the target operation of the current operation account on the target software can be directly refused, and a corresponding prompt can be issued to prompt the user that the operation authority is not available.

[0059] In an optional implementation, the target operation may include operations such as install, update, list, and upgrade. Among them, the install operation indicates installing a software package; the update operation indicates updating a software package to the latest version; the list operation indicates listing software package information; and the upgrade operation indicates updating all software packages to the latest version. Compared with the update operation, it pays more attention to processing changes in dependency relationships and is more suitable for processing load dependencies.

[0060] Step S102: Generate an operation request instruction based on the token information and the operation type of the target operation, and send the operation request instruction to the server.

[0061] In an embodiment of the present invention, a corresponding request is formed according to the operation type of the target operation. For example, if the operation type of the target operation is installation, an install request is generated. After obtaining the token information of the current operation account, the token information is stored in the token parameter corresponding to the request header, such as {Auth Token: token information}, thereby generating an operation request instruction, and sending the operation request instruction to the server, so that the server performs permission verification according to the operation request instruction.

[0062] In an embodiment of the present invention, the Auth Yum Server server is used to perform permission verification on the target operation based on the operation request instruction, and return the permission verification result to the client. The permission verification result is used to indicate whether the current operating account has the permission to perform the target operation on the target software, which may include authorization success and authorization failure; if the permission verification result is authorization success, it indicates that the current operating account has the permission to perform the target operation on the target software; if the permission verification result is authorization failure, it indicates that the current operating account does not have the permission to perform the target operation on the target software.

[0063] Step S103, obtaining the permission verification result sent by the server, and performing the authorization action corresponding to the permission verification result on the target operation.

[0064] In the embodiment of the present invention, the permission verification result sent by the Auth Yum Server is obtained, and according to the permission verification result, the corresponding authorization action is performed on the target operation, that is, the target operation is authorized to be executed, or the target operation is not authorized to be executed.

[0065] In an optional implementation, if the permission check result is authorization success, it indicates that the current operating account has the permission to perform the target operation on the target software, so the target operation can be authorized, and the target operation of the current operating account on the target software is performed. If the permission check result is authorization failure, it indicates that the current operating account does not have the permission to perform the target operation on the target software, so the target operation is not authorized, and the target operation of the current operating account on the target software is not performed.

[0066] On the other hand, a software permission management method is provided in this embodiment, which can be used in a server, namely, AuthYum Server. Auth Yum Server can be an independent server for performing identity authentication and authorization management on accounts that perform software-related operations in AuthYum clients. Figure 2 is a flowchart of a software rights management method according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0067] Step S201, in response to the operation request instruction sent by the client, the operation request instruction is parsed to obtain token information and the operation type of the target operation.

[0068] In an embodiment of the present invention, in response to an operation request instruction sent by an AuthYum client, the operation request instruction is parsed; first, the operation type of the target operation is determined according to the type of the operation request instruction. For example, if the operation request instruction is an install request, then it can be determined that the operation type of the target operation is installation; then, the Auth Token parameter in the request is extracted from the operation request instruction to obtain the token information of the current operation account.

[0069] Step S202, deserialize the token information to obtain the current operating account, and perform account verification on the current operating account based on the account information of the current operating account.

[0070] In the embodiment of the present invention, the token information is deserialized to obtain the current operating account, specifically, the user name of the current operating account. Then, the account information corresponding to the current operating account is queried and obtained from the database corresponding to the Auth Yum Server service end, and the account information of the current operating account is compared to realize the account verification of the current operating account.

[0071] In an optional implementation, the account information includes the account status of the current operating account, and the account status is used to characterize whether the current operating account can be used normally. Accordingly, the account verification of the current operating account includes the following steps: obtaining the account status corresponding to the current operating account; if the account status is the first state, determining that the account verification of the current operating account has passed; if the account status is the second state, determining that the account verification of the current operating account has failed. Among them, the first state is a state in which the current operating account can be used normally, and the second state is a state in which the current operating account cannot be used normally, such as a frozen state. Thus, the identity verification of the current operating account is implemented by verifying the account status, ensuring that the current operating account can be used normally when performing the target operation on the target software, thereby improving the security and reliability of software management.

[0072] In an optional implementation, the account information includes the account token of the current operating account. The account token of each operating account is stored in the database corresponding to the Auth YumServer server, so that the token of each operating account is stored locally in the database and the AuthYum client, and the two tokens stored are compared and verified to verify whether the information of the operating account is consistent in the AuthYum client and the Auth Yum Server server, thereby verifying the data security and reliability of the operating account. Specifically, the account verification of the current operating account includes the following steps: obtaining the account token corresponding to the current operating account; if the token information is consistent with the account token, determining that the account verification of the current operating account has passed; if the token information is inconsistent with the account token, determining that the account verification of the current operating account has failed.

[0073] Step S203: If the account verification of the current operating account passes, then based on the permission information of the current operating account, the operation type of the target operation is verified, a permission verification result is obtained, and the permission verification result is returned to the client.

[0074] In an embodiment of the present invention, if the account verification of the current operating account passes, the operation authority of the current operating account is further verified, that is, whether the current operating account has the authority to perform the target operation on the target software. Specifically, the authority information of the current operating account is obtained, and the operation type of the target operation is verified through the authority information to obtain the authority verification result. After obtaining the authority verification result, it is returned to the AuthYum client, so that the AuthYum client performs the corresponding authorization action on the target operation according to the authority verification result.

[0075] In an optional implementation, the permission information includes at least one operation permission, and each operation permission corresponds to an operation type. The permission information is compared with the operation type; if the permission information includes the permission corresponding to the operation type, it indicates that the current operation account has the permission to perform the target operation on the target software, so the permission verification result is determined to be authorization success; if the permission information does not include the permission corresponding to the operation type, it indicates that the current operation account does not have the permission to perform the target operation on the target software, so the permission verification result is determined to be authorization failure.

[0076] In an optional implementation, in order to facilitate user operations, the present invention also includes steps related to the creation and management of operating accounts. Among them, the creation of operating accounts is achieved through an administrator account, which is an account with all permissions. Using the administrator account, the first operating account can be created in the client and the token information of the first operating account can be saved. Specifically, after the Auth Yum Server service end is started, the administrator account will be initialized, and the token information of the administrator account will be configured, and then the administrator account and its token information will be output to the AuthYum client to be stored locally in the AuthYum client, so that the administrator account can be called in the AuthYum client to create the first operating account; when the administrator account is used to create the first operating account, the user enters the user name and permissions in the account creation command, and the token information and permission information of the first operating account are obtained according to the account creation command, and the token information is stored locally in the AuthYum client. At the same time, the Auth Yum Server service end responds to the account creation request output by the administrator account, obtains and saves the account information and permission information of the first operating account.

[0077] In a specific embodiment, Figure 3 is a flowchart of a specific implementation of the software rights management method according to an embodiment of the present invention. Figure 3 Taking the software rights management method of the present invention as an example, the software rights management method of the present invention is further explained.

[0078] like Figure 3 As shown, the user uses the user1 operation account to operate the AuthYum client. The AuthYum client obtains the token information auth_token of the user1 operation account from the local / etc / yum.conf file, and generates a corresponding operation request instruction based on this. The request header of the operation request instruction carries the token information auth_token of the user1 operation account, that is, it includes {Auth Token: $auth_token}.

[0079] The Auth Yum Server parses the operation request instruction to obtain the token information auth_token; deserializes the token information auth_token to obtain the user name user1 of the user1 operation account; then obtains the corresponding user name and account token token from the database based on the user name user1 for identity authentication. If the identity authentication fails, http_code:401 is returned to the AuthYum client as the response result of the Auth Yum Server server; if the identity authentication passes, authorization verification is performed to obtain the permission information of the user1 operation account from the database to confirm whether the operation of the user1 operation account is authorized. If the authorization is successful, http_code:200 is returned to the AuthYum client as the response result of the Auth YumServer server; if the authorization fails, http_code:403 is returned to the AuthYum client as the response result of the Auth Yum Server server.

[0080] Finally, the AuthYum client determines whether to execute the operation of user1's account based on the response result returned by the Auth Yum Server. If the response result returned is http_code:200, the operation of user1's account will be executed; if the response result returned is not http_code:200, the operation of user1's account will not be executed, and the corresponding error code will be returned.

[0081] The software permission management method provided by the embodiment of the present invention generates an operation request instruction based on the token information of the current operation account and the operation type of the target operation, performs permission verification on the target operation based on the operation request instruction through the server, and returns the permission verification result to the client, so that the client executes the authorization action corresponding to the permission verification result on the target operation, thereby performing identity authentication and authorization management before operating the software, thereby improving the security and reliability of software management.

[0082] In this embodiment, a software rights management device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0083] On the one hand, this embodiment provides a software rights management device, which is applied to a client, such as Figure 4 As shown, including:

[0084] The token acquisition module 401 is used to acquire the token information of the current operating account in response to the target operation of the current operating account on the target software;

[0085] The instruction generation module 402 is used to generate an operation request instruction based on the token information and the operation type of the target operation, and send the operation request instruction to the server; the server is used to perform permission verification on the target operation based on the operation request instruction, and return the permission verification result to the client;

[0086] The action execution module 403 is used to obtain the permission verification result sent by the server, and execute the authorization action corresponding to the permission verification result on the target operation.

[0087] In an optional implementation, the action execution module 403 includes:

[0088] The authorization success unit is used to execute the target operation of the current operating account on the target software if the permission verification result is authorization success;

[0089] The authorization failure unit is used to not execute the target operation of the current operating account on the target software if the permission verification result is authorization failure.

[0090] On the other hand, this embodiment provides a software rights management device, which is applied to a server, such as Figure 5 As shown, including:

[0091] The instruction parsing module 501 is used to respond to the operation request instruction sent by the client, parse the operation request instruction, and obtain token information and the operation type of the target operation;

[0092] An account verification module 502 is used to deserialize the token information, obtain the current operating account, and perform account verification on the current operating account based on the account information of the current operating account;

[0093] The permission verification module 503 is used to perform permission verification on the operation type of the target operation based on the permission information of the current operation account if the account verification of the current operation account passes, obtain the permission verification result, and return the permission verification result to the client.

[0094] In an optional implementation, the account verification module 502 includes:

[0095] An account status acquisition unit, used to acquire the account status corresponding to the current operating account;

[0096] An account verification passing unit, used to determine that the account verification of the current operating account has passed if the account status is the first status;

[0097] The account verification failure unit is used to determine that the account verification of the current operating account has failed if the account status is the second status.

[0098] In an optional implementation, the account verification module 502 includes:

[0099] An account token acquisition unit, used to acquire the account token corresponding to the current operating account;

[0100] The account verification passing unit is also used to determine that the account verification of the current operating account has passed if the token information is consistent with the account token;

[0101] The account verification failure unit is also used to determine that the account verification of the current operating account has failed if the token information is inconsistent with the account token.

[0102] In an optional implementation, the permission verification module 503 includes:

[0103] The permission information corresponding unit is used to compare the permission information with the operation type;

[0104] An authorization success unit, used to determine that the permission verification result is authorization success if the permission information contains the permission corresponding to the operation type;

[0105] The authorization failure unit is used to determine that the permission verification result is an authorization failure if the permission information does not contain the permission corresponding to the operation type.

[0106] In an optional embodiment, the device further comprises:

[0107] An administrator account configuration module is used to initialize the administrator account and configure the token information of the administrator account; the administrator account is used to create a first operation account in the client and save the token information of the first operation account;

[0108] The operating account creation module is used to obtain and save the account information and permission information of the first operating account in response to the account creation request output by the administrator account.

[0109] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0110] The software rights management device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0111] The embodiment of the present invention also provides a computer device having the above Figure 4 or Figure 5 The software rights management device shown.

[0112] See also Figure 6 , Figure 6 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 6 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 6 A processor 10 is taken as an example.

[0113] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0114] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0115] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0116] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0117] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0118] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0119] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0120] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the present invention.

Claims

1. A software rights management method, characterized in that: Applied in a client, the method includes: In response to the target operation of the current operating account on the target software, acquiring token information of the current operating account; Based on the token information and the operation type of the target operation, an operation request instruction is generated, and the operation request instruction is sent to the server; the server is used to perform permission verification on the target operation based on the operation request instruction, and return the permission verification result to the client; Obtain the permission verification result sent by the server, and perform the authorization action corresponding to the permission verification result on the target operation.

2. The method according to claim 1, characterized in that The performing of the authorization action corresponding to the permission verification result on the target operation includes: If the permission verification result is authorization success, executing the target operation of the current operating account on the target software; If the permission check result is authorization failure, the target operation of the current operating account on the target software will not be performed.

3. A software rights management method, characterized in that: Applied in the server, the method includes: In response to the operation request instruction sent by the client, the operation request instruction is parsed to obtain token information and the operation type of the target operation; Deserialize the token information to obtain the current operating account, and perform account verification on the current operating account based on the account information of the current operating account; If the account verification of the current operating account passes, then based on the permission information of the current operating account, a permission verification is performed on the operation type of the target operation to obtain a permission verification result, and the permission verification result is returned to the client.

4. The method according to claim 3, characterized in that The performing account verification on the current operating account based on the account information of the current operating account includes: Obtain the account status corresponding to the current operating account; If the account status is the first status, determining that the account verification of the current operating account has passed; If the account status is the second status, it is determined that the account verification of the current operating account has failed.

5. The method according to claim 3, characterized in that: The performing account verification on the current operating account based on the account information of the current operating account includes: Obtain the account token corresponding to the current operating account; If the token information is consistent with the account token, it is determined that the account verification of the current operating account has passed; If the token information is inconsistent with the account token, it is determined that the account verification of the current operating account has failed.

6. The method according to claim 3, characterized in that The step of performing permission verification on the operation type of the target operation based on the permission information of the current operation account to obtain a permission verification result includes: Comparing the permission information with the operation type; If the permission information includes the permission corresponding to the operation type, determining that the permission verification result is authorization success; If the permission information does not include the permission corresponding to the operation type, it is determined that the permission verification result is an authorization failure.

7. The method according to claim 6, characterized in that The method further comprises: Initialize an administrator account and configure the token information of the administrator account; the administrator account is used to create a first operation account in the client and save the token information of the first operation account; In response to the account creation request output by the administrator account, the account information and permission information of the first operation account are obtained and saved.

8. A software rights management device, characterized in that: Applied in a client, the device comprises: A token acquisition module, used to acquire token information of the current operating account in response to the target operation of the current operating account on the target software; An instruction generation module is used to generate an operation request instruction based on the token information and the operation type of the target operation, and send the operation request instruction to the server; the server is used to perform permission verification on the target operation based on the operation request instruction, and return the permission verification result to the client; The action execution module is used to obtain the permission verification result sent by the server and execute the authorization action corresponding to the permission verification result on the target operation.

9. A software rights management device, characterized in that: Applied in a server, the device comprises: An instruction parsing module, used to respond to an operation request instruction sent by a client, parse the operation request instruction, and obtain token information and an operation type of a target operation; An account verification module, used to deserialize the token information, obtain the current operating account, and perform account verification on the current operating account based on the account information of the current operating account; The permission verification module is used to perform permission verification on the operation type of the target operation based on the permission information of the current operation account if the account verification of the current operation account passes, obtain the permission verification result, and return the permission verification result to the client.

10. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the software rights management method according to any one of claims 1 to 2 or 3 to 7 by executing the computer instructions.

Images