CN110874219A - Task authority control method and device - Google Patents
Task authority control method and device Download PDFInfo
- Publication number
- CN110874219A CN110874219A CN201911114769.5A CN201911114769A CN110874219A CN 110874219 A CN110874219 A CN 110874219A CN 201911114769 A CN201911114769 A CN 201911114769A CN 110874219 A CN110874219 A CN 110874219A
- Authority
- CN
- China
- Prior art keywords
- subtask
- account
- task
- processing
- applicant
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Storage Device Security (AREA)
Abstract
The application provides a task authority control method and device, wherein the method comprises the following steps: receiving a task sheet sent by a first applicant account, wherein the task sheet comprises at least one subtask sheet, and the subtask sheet comprises information of a target code and information of processing permission required by the target code; sending the task list to an approver; and respectively granting the processing permission required by the target code corresponding to each subtask sheet to the first applicant account under the condition that the instruction that the examining and approving party agrees that the first applicant account obtains the processing permission is received. The method and the device have the advantages that the first applicant account is prevented from having unnecessary processing permission on the target code, and only the first applicant account is prevented from having processing permission, all codes can be edited and modified.
Description
Technical Field
The present application relates to the field of network security technologies, and in particular, to a method and an apparatus for controlling task permission, a computing device, and a computer-readable storage medium.
Background
When editing a scene of an online game or testing the game, multiple persons are required to perform cooperative processing on related codes together, processing permission on the codes is required to be applied before the codes or resources are cooperatively processed, and the codes can be processed after the processing permission on the codes is obtained. The code processing authority is generally obtained through a code authority control system.
In the prior art, a code authority control system includes an open source code version control System (SVN) and an open source distributed version control system (GIT), the SVN is used for efficiently managing by adopting a branch management system, in short, the SVN is used for developing the same project by multiple persons together, so as to realize resource sharing and finally centralized management, the SVN realizes authority control by personal accounts, so as to realize the opening and closing of the authority of a single account, when the authority is opened for a certain account, all codes can be edited and modified, when the authority is closed, any code cannot be edited and modified, the flexibility of account authority control is poor, and the normal operation of development tasks is influenced.
The GIT is an open-source distributed version control system, when a plurality of persons edit and modify codes, the GIT is controlled through a directory, namely, a super-large modification right, including a right to a target modification code and other unnecessary modification rights, is transferred to an account through the directory, and a programmer carries out misoperation or malicious operation on the codes through the unnecessary modification rights to influence the normal and orderly progress of development tasks.
Disclosure of Invention
In view of this, embodiments of the present application provide a method and an apparatus for controlling permission of a task, a computing device, and a computer-readable storage medium, so as to solve technical defects in the prior art.
The embodiment of the application discloses a task authority control method, which comprises the following steps:
receiving a task sheet sent by a first applicant account, wherein the task sheet comprises at least one subtask sheet, and the subtask sheet comprises information of a target code and information of processing permission required by the target code;
sending the task list to an approver;
and respectively granting the processing permission required by the target code corresponding to each subtask sheet to the first applicant account under the condition that the instruction that the examining and approving party agrees that the first applicant account obtains the processing permission is received.
The embodiment of the application discloses authority control device of task, includes:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is configured to receive a task sheet sent by a first applicant account, the task sheet comprises at least one subtask sheet, and the subtask sheet comprises information of a target code and information of processing authority required by the target code;
the sending module is configured to send the task list to an approver;
and the authorization module is configured to grant the processing permission required by the target code corresponding to each subtask sheet to the first applicant account respectively under the condition that the instruction that the first applicant account obtains the processing permission is received by the approval party.
The embodiment of the application discloses computing equipment, which comprises a memory, a processor and computer instructions stored on the memory and capable of running on the processor, wherein the processor executes the instructions to realize the steps of the authority control method of the task.
The embodiment of the application discloses a computer readable storage medium, which stores computer instructions, and the instructions are executed by a processor to realize the steps of the authority control method of the task.
According to the method and the device, the processing permission required by the target code corresponding to each subtask list is granted to the first applicant account respectively, so that the first applicant account is prevented from having unnecessary processing permission on the target code, only the first applicant account is prevented from having processing permission, and all codes can be edited and modified.
Drawings
FIG. 1 is a schematic block diagram of a computing device according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating a task authority control method according to a first embodiment of the present application;
FIG. 3 is a schematic flow chart of a task permission control method according to a second embodiment of the present application;
FIG. 4 is a flow chart illustrating the process of recovering processing rights in the rights control method of the task in the present application;
FIG. 5 is a schematic flow chart of a task authority control method according to a third embodiment of the present application;
fig. 6 is a schematic structural diagram of a task authority control device according to a fourth embodiment of the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In the present application, a method and an apparatus for controlling authority of task, a computing device and a computer readable storage medium are provided, and detailed descriptions are individually provided in the following embodiments.
Fig. 1 is a block diagram illustrating a configuration of a computing device 100 according to an embodiment of the present specification. The components of the computing device 100 include, but are not limited to, memory 110 and processor 120. The processor 120 is coupled to the memory 110 via a bus 130 and a database 150 is used to store data.
Computing device 100 also includes access device 140, access device 140 enabling computing device 100 to communicate via one or more networks 160. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. Access device 140 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the present description, the above-described components of computing device 100 and other components not shown in FIG. 1 may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 1 is for purposes of example only and is not limiting as to the scope of the description. Those skilled in the art may add or replace other components as desired.
Computing device 100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), a mobile phone (e.g., smartphone), a wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 100 may also be a mobile or stationary server.
Wherein the processor 120 may perform the steps of the method shown in fig. 2. Fig. 2 is a schematic flowchart showing a method of controlling authority of a task according to a first embodiment of the present application, including steps 202 to 206.
Step 202: receiving a task sheet sent by a first applicant account, wherein the task sheet comprises at least one subtask sheet, and the subtask sheet comprises information of a target code and information of processing permission required by the target code.
The first applicant account can send the task form by means of mail, the mailbox account for sending the task form can be used as the first applicant account, and certainly, the first applicant account can send the task form by means of other methods.
The task list can comprise two subtask lists, three subtask lists or four subtask lists, and the number of the subtask lists in the task list is not limited in the application.
The task sheet may be a total game development task, a subtask sheet in the task sheet may be a task for developing one function in a game, the subtask sheet includes information of an object code required for developing a game function and information of a processing right required for the object code, the information of the object code in the subtask sheet may be a storage path where the object code is located or a code library where the object code is located, and the subtask sheet may further include a reason for obtaining the object code.
The information of the processing right required by the object code may be at least one of a readable right, an editing right and a submitting right, and the processing right required by the object code may also be other rights, which is not limited in this application.
It should be noted that the readable right is that the first requestor account has a right to read the target code, and cannot modify or store the target code; the editing authority is the authority of the first requester account number for editing and modifying the target code; the submission authority is the authority for submitting the target codes corresponding to the task sheet after the target codes corresponding to the task sheet are processed, and the first requester account with the submission authority can submit the target codes corresponding to the subtask sheet so as to complete the subtask sheet.
Step 204: and sending the task list to an approver.
After the task list is sent to the approval party, the approval party explains the reason for processing the target code according to the task list, and the information of the target code in the task list and the information of the processing authority required by the target code are checked.
Step 206: and respectively granting the processing permission required by the target code corresponding to each subtask sheet to the first applicant account under the condition that the instruction that the examining and approving party agrees that the first applicant account obtains the processing permission is received.
The first requestor account has a processing right required by the target code corresponding to each subtask sheet, for example, the task sheet includes a first subtask sheet and a second subtask sheet, the first subtask sheet includes information of a first target code and information of a first processing right required by the first target code, the second subtask sheet includes information of a second target code and information of a second processing right required by the second target code, and the first requestor account is respectively granted with the first processing right required by the first target code corresponding to the first subtask sheet and the second processing right required by the second target code corresponding to the second subtask sheet.
Therefore, the first applicant account corresponding to the first subtask sheet only has the first processing permission required by the first target code, and the first applicant account corresponding to the second subtask sheet only has the second processing permission required by the second target code, so that the first applicant account is prevented from having unnecessary processing permission on the target code, and only the first applicant account is prevented from having processing permission, all codes can be edited and modified.
It should be noted that other first requestor accounts can also have the processing authority required by the object code corresponding to the subtask list, which is schematically described below by way of example.
The first requestor account a1 has the editing right required by the target code1 corresponding to the subtask list T1, and the first requestor account a1 also has the editing right and submission right required by the target code2 corresponding to the subtask list T2;
the first requestor account a2 has readable permission required by the target code1 corresponding to the subtask list T1; the first requestor account a3 has editing authority required by the target code1 corresponding to the subtask list T1; the first requestor account a4 has editing authority required by the target code2 corresponding to the subtask list T2. According to the required workload and the actual requirement of the subtask list T1, the number of the first requester accounts grants the processing authority required by the corresponding target code of the subtask list T1, and the subtask list can be normally completed.
The step 206 specifically includes steps 2062 to 2064.
Step 2062: and determining the directory where the target code is located according to the information of the target code in each subtask list.
And determining the directory where the target code is located according to the storage position where the target code is located in the information of the target code in each subtask list.
Step 2064: and granting the processing authority required by the code under the directory to the first requester account which sends the task list.
According to the method and the device, the processing permission of the directory where the target code is located is granted to the first applicant account, namely, the first applicant account can edit all codes under the directory, and the granting of the processing permission required by the codes under the directory to the first applicant account can be facilitated.
In the embodiment, the processing permission required by the target code corresponding to each subtask list is respectively granted to the first applicant account, so that the first applicant account is prevented from having unnecessary processing permission on the target code, and only the first applicant account is prevented from having processing permission, all codes can be edited and modified.
Fig. 3 is a schematic flowchart illustrating a method of controlling authority of a task according to a second embodiment of the present application, including steps 302 to 316.
Step 302: receiving a task sheet sent by a first applicant account, wherein the task sheet comprises at least one subtask sheet, and the subtask sheet comprises information of a target code and information of processing permission required by the target code.
Step 304: and sending the task list to an approver.
Step 306: and respectively granting the processing permission required by the target code corresponding to each subtask sheet to the first applicant account under the condition that the instruction that the examining and approving party agrees that the first applicant account obtains the processing permission is received.
The above steps 302 to 306 refer to the descriptions of the steps 202 to 206 in the first embodiment, and are not repeated here.
Step 308: and determining the number of the subtask sheet based on the subtask sheet in the task sheet sent by the first requester account.
The number of the subtask single may be determined according to the sending time plus the serial number, for example, if the sending time of one subtask single in the task list is 12 o' clock 00/12/03/08/2019, and the serial number of the subtask single is 01, it is determined that the number of the subtask single may be 20190803120001, and the number of another subtask single in the task list may be 20190803120002, or certainly, the number of the subtask single may be determined according to other rules.
Step 310: and associating the subtask single number with the first requester account with the submission authority and storing the subtask single number and the first requester account into a task table.
The first applicant account has a submission permission for a target code corresponding to the subtask single number, and the subtask single number is associated with the first applicant account, for example, the subtask single number 20190803120001 is associated with the first applicant account a1 having the submission permission, and the subtask single number 20190803120002 is associated with the first applicant account a1 and then stored in a task table. In addition, a single subtask sheet number may be associated with the plurality of first requestor accounts, the subtask sheet number 20190803120001 may be associated with the first requestor account a2 and the first requestor account a3, and the subtask sheet number 20190803120002 may be associated with the first requestor account a 4.
Step 312: and receiving a coded request corresponding to the subtask single number submitted by a second applicant account, and determining the first applicant account related to the subtask single number in the task list according to the subtask single number.
The coded codes are codes obtained after the target codes are edited and modified by the second applicant account, the second applicant account submits the edited codes after the target codes are edited and modified, and the second applicant account is the right to be verified whether to submit the subtask single number or not.
Step 314: and comparing the second applicant account with the first applicant account determined in the task table.
In this step, the second requestor account is compared with each first requestor account determined in the task table.
Step 316: and under the condition that the second applicant account number is the same as any one of the first applicant account numbers determined in the task table, submitting the coded codes corresponding to the subtask single number, and recovering the processing permission of the second applicant account number associated with the subtask single number to the target codes.
In the step, according to the coded codes corresponding to the subtask single numbers to be submitted by the second applicant account, the first applicant account related to the subtask single numbers is searched in the task table based on the subtask single numbers, and under the condition that the second applicant account is the same as any one of the first applicant accounts determined in the task table, the second applicant account has the submission permission of the coded codes corresponding to the subtask single numbers, so that the second applicant account is determined to be capable of submitting the coded codes corresponding to the subtask single numbers, the problem that the codes are submitted by the second applicant account not having the permission corresponding to the subtask single numbers is avoided, and the smooth completion of the subtask single numbers is ensured.
In addition, only the processing authority of the second requester account associated with the subtask single number to the target code is recovered, for example, the second requester account a1 has the editing authority and submission authority of the target code1 to the subtask single T1, the second requester account a1 has the editing authority and submission authority of the target code2 to the subtask single T2, only the editing authority and submission authority of the second requester account a1 associated with the single number of the subtask single T1 to the target code1 are recovered, the editing authority of the object code2 corresponding to the subtask list T2 is not affected by the second requestor account a1, so that when the processing authority of the second requestor account a1 is recovered, the editing of the object code2 corresponding to the subtask list T2 by the second requestor account a1 is affected, the processing authority of the first applicant account a1 can be accurately recovered, and development tasks are guaranteed to be efficiently carried out.
Referring to fig. 4, the step 316 includes steps 402 to 406.
Step 402: and setting the recovery time for recovering the processing authority of the second requester account related to the subtask single number.
The recovery time for recovering the processing authority of the second requester account number associated with the subtask single number can be set to be 5 minutes or 1 hour, and the recovery time after the coded code corresponding to the subtask single number is submitted is determined according to the actual situation of the subtask single.
Step 404: and recording the submission time after the coded corresponding to the subtask single number is submitted.
In this step, the second requester account starts to record the submission time as long as the second requester account submits the coded code corresponding to the subtask single number.
Step 406: and recovering the processing permission of the second applicant account related to the subtask single number under the condition that the submission time exceeds the recovery time.
After the second applicant account number submits the coded codes corresponding to the subtask single number for the first time, the programmer further needs to switch to other coded codes corresponding to the subtask single number and submit the other coded codes corresponding to the subtask single number, if the programmer does not completely submit the coded codes corresponding to the subtask single number, the authority of the second applicant account number is directly recovered, the programmer further needs to re-apply the processing authority required by the target codes corresponding to the subtask single number, the processing progress of the subtask single is delayed, and the processing efficiency of the task list is affected.
According to the method and the device, the recovery time for recovering the processing permission of the second applicant account number associated with the subtask single number is set, so that the processing permission of the second applicant account number associated with the subtask single number is recovered under the condition that the submission time exceeds the recovery time in the following steps, the fact that programmers can submit all coded codes corresponding to the subtask single number through the second applicant account number is guaranteed, the recovery flexibility of the processing permission corresponding to the subtask single number is improved, the subtask single can be completed efficiently, and efficient completion of the whole task list is guaranteed.
An application scenario of the present embodiment is schematically described below.
For example, a first subtask list T1 and a second subtask list T2 in a task list sent by a first requestor account a1 are received, the first subtask list T1 includes information of a first target code1 and editing authority required by the first target code1, and the second subtask list T2 includes information of a second target code2 and editing and submitting authority required by the second target code 2.
And sending the first subtask list T1 and the second subtask list T2 to an approver.
And under the condition that the command that the approver agrees that the first applicant account a1 obtains the editing right corresponding to the first subtask list and the editing and submitting right corresponding to the second subtask list T2 is received, the editing right required by the first target code1 is granted to the first applicant account a1, and the editing and submitting right required by the second target code2 is granted to the first applicant account a 1.
The sending time of the first subtask bill T1 in the task list is 12: 00 points on 03/08/2019, the serial number of the subtask bill T1 is 01, it is determined that the bill number of the first subtask bill T1 can be 20190803120001, the bill number of the second subtask bill T2 in the task list can be 20190803120002,
the sheet number 20190803120002 of the second subtask sheet T2 and the first requester account a1 with the submitting right are associated and stored in the task table, and in addition, the task table may also have the first requester account a2 with the submitting right associated with the sheet number 20190803120002 of the second subtask sheet T2.
When a request that a second requester account submits a coded code corresponding to the single number 20190803120002 of the second subtask list T2 is received, the first requester accounts a1 and a2 associated with the single number 20190803120002 of the second subtask list T2 in the task table are determined according to the single number 20190803120002 of the second subtask list T2.
And under the condition that the second requester account is the same as any one of the first requester accounts determined in the task table, submitting the coded code corresponding to the single number 20190803120002 of the second subtask list T2, and recovering the processing permission of the second requester account related to the single number 20190803120002 of the second subtask list T2 on the target code. The method and the device avoid the problem that the normal operation of the development task is influenced due to disordered code submission caused by the fact that the account number of the second requester does not have the authority corresponding to the subtask list number submits the code, and ensure that the subtask list can be successfully completed.
Fig. 5 is a schematic flowchart illustrating a method of controlling authority of a task according to a third embodiment of the present application, including steps 502 to 510.
Step 502: receiving a task sheet sent by a first applicant account, wherein the task sheet comprises at least one subtask sheet, and the subtask sheet comprises information of a target code and information of processing permission required by the target code.
Step 504: and sending the task list to an approver.
Step 506: and respectively granting the processing permission required by the target code corresponding to each subtask sheet to the first applicant account under the condition that the instruction that the examining and approving party agrees that the first applicant account obtains the processing permission is received.
Respectively granting processing permission required by the target code corresponding to each subtask list to a first requester account, and receiving a predetermined plan sent by the first requester account, wherein the predetermined plan comprises a predetermined time period and a predetermined task list, and the predetermined task list comprises information of the target code and information of the processing permission required by the target code; sending the predetermined plan to an approver; and under the condition that an instruction that the approving party agrees to the predetermined plan is received, the processing permission required by the target code in the predetermined task list is granted to the first requester account in the predetermined time period. The number of the first requester accounts may be one or more.
Step 508: and setting the processing time of the first applicant account with the processing authority corresponding to the subtask list.
After the first applicant account is respectively granted with the processing permission required by the target code corresponding to each subtask list, the processing time of the first applicant account having the processing permission corresponding to the subtask list is set according to the processing time required by the actual task amount of the subtask list.
Step 510: and under the condition that the time that the first requester account has the processing permission exceeds the processing time, recovering the processing permission of the target code corresponding to the first requester account.
In the embodiment, when the time that the first applicant account has the processing permission exceeds the processing time, the processing permission of the target code corresponding to the first applicant account is recovered, the time that the first applicant account has the processing permission corresponding to the subtask sheet is flexibly controlled, the situation that the first applicant account continuously has the processing permission of the target code corresponding to the subtask sheet is avoided, the target code corresponding to the subtask sheet is prevented from being operated by a programmer by mistake or maliciously operated by the programmer, the development task is efficiently carried out, and the processing permission required by the target code corresponding to each subtask sheet is respectively granted to the first applicant account, so that the first applicant account is prevented from having unnecessary processing permission on the target code, and only the first applicant account is prevented from having the processing permission, the method and the device can edit and modify all codes, the first applicant can only have specific processing permission on the specific target codes corresponding to the subtask list, the flexibility of control over the processing permission of the account of the first applicant is high, a programmer is prevented from carrying out misoperation or malicious operation on the codes through unnecessary modification permission, the development task is ensured to be carried out normally and orderly, and the development efficiency is improved.
Fig. 6 is a schematic configuration diagram showing a rights control apparatus of a task according to a fourth embodiment of the present application, including:
a receiving module 602, configured to receive a task form sent by a first requestor account, where the task form includes at least one subtask form, and the subtask form includes information of a target code and information of a processing permission required by the target code;
a sending module 604 configured to send the task list to an approver;
an authorization module 606 configured to grant, to the first requestor account, the processing permission required by the target code corresponding to each subtask sheet, respectively, when receiving an instruction that the approver agrees that the first requestor account obtains the processing permission.
The authorization module 606 is further configured to determine a directory where the object code is located according to information of the object code in each subtask list;
and granting the processing authority required by the code under the directory to the first requester account which sends the task list.
The authority control device of the task further comprises:
the first determination module is configured to determine a subtask sheet number based on a subtask sheet in a task sheet sent by a first requester account;
the association module is configured to associate the subtask single number with a first requester account with submission permission and store the subtask single number and the first requester account into a task table;
the second determination module is configured to receive a coded request corresponding to the subtask single number submitted by a second applicant account, and determine the first applicant account associated with the subtask single number in the task table according to the subtask single number;
the comparison module is configured to compare the second applicant account with the first applicant account determined in the task table;
and the recovery module is configured to submit the coded codes corresponding to the subtask single number and recover the processing permission of the second requester account related to the subtask single number to the target codes under the condition that the second requester account is the same as any one of the first requester accounts determined in the task table.
The authority control device of the task further comprises:
the setting module is configured to set the processing time that the first requester account has the processing authority corresponding to the subtask list;
and the reclaiming module is configured to reclaim the processing permission of the target code corresponding to the first requester account under the condition that the time that the first requester account has the processing permission exceeds the processing time.
The recovery module is further configured to set recovery time for recovering the processing authority of the second requester account associated with the subtask single number;
recording the submission time after submitting the coded corresponding to the subtask single number;
and recovering the processing permission of the second applicant account related to the subtask single number under the condition that the submission time exceeds the recovery time.
The receiving module is further configured to receive a predetermined plan sent by a first requester account, wherein the predetermined plan comprises a predetermined time period and a predetermined task list, and the predetermined task list comprises information of a target code and information of processing authority required by the target code;
the sending module is further configured to send the predetermined plan to an approver;
the granting module is further configured to grant the processing authority required by the target code in the predetermined task list to the first requester account in the predetermined time period under the condition that the instruction of the predetermined plan is approved by the approving party.
In the embodiment, the processing permission required by the target code corresponding to each subtask list is respectively granted to the first applicant account, so that the first applicant account is prevented from having unnecessary processing permission on the target code, and only the first applicant account is prevented from having processing permission, all codes can be edited and modified.
An embodiment of the present application further provides a computing device, which includes a memory, a processor, and computer instructions stored in the memory and executable on the processor, where the processor executes the instructions to implement the steps of the method for controlling the permission of the task.
An embodiment of the present application further provides a computer readable storage medium, which stores computer instructions, and when the instructions are executed by a processor, the instructions implement the steps of the method for controlling the authority of the task.
The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the method for controlling the authority of the task belong to the same concept, and details that are not described in detail in the technical solution of the storage medium can be referred to the description of the technical solution of the method for controlling the authority of the task.
The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
It should be noted that, for the sake of simplicity, the above-mentioned method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The preferred embodiments of the present application disclosed above are intended only to aid in the explanation of the application. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the application and the practical application, to thereby enable others skilled in the art to best understand and utilize the application. The application is limited only by the claims and their full scope and equivalents.
Claims (10)
1. A task authority control method is characterized by comprising the following steps:
receiving a task sheet sent by a first applicant account, wherein the task sheet comprises at least one subtask sheet, and the subtask sheet comprises information of a target code and information of processing permission required by the target code;
sending the task list to an approver;
and respectively granting the processing permission required by the target code corresponding to each subtask sheet to the first applicant account under the condition that the instruction that the examining and approving party agrees that the first applicant account obtains the processing permission is received.
2. The method of claim 1, wherein granting the first requestor account with the processing permission required by the target code corresponding to each subtask list respectively comprises:
determining a directory where the target code is located according to the information of the target code in each subtask list;
and granting the processing authority required by the code under the directory to the first requester account which sends the task list.
3. The method of claim 1, wherein after receiving the task form sent by the first requestor account, the method further comprises:
determining a subtask list number based on a subtask list in a task list sent by a first requester account;
associating the subtask single number with a first requester account with a submission authority and storing the first requester account into a task table;
receiving a coded request corresponding to the subtask single number submitted by a second applicant account, and determining the first applicant account related to the subtask single number in the task list according to the subtask single number;
comparing the second applicant account with the first applicant account determined in the task table;
and under the condition that the second applicant account number is the same as any one of the first applicant account numbers determined in the task table, submitting the coded codes corresponding to the subtask single number, and recovering the processing permission of the second applicant account number associated with the subtask single number to the target codes.
4. The method of claim 3, after the processing right required by the target code corresponding to each subtask list is respectively granted to the first requestor account, further comprising:
setting the processing time of the first applicant account with the processing authority corresponding to the subtask list;
and under the condition that the time that the first requester account has the processing permission exceeds the processing time, recovering the processing permission of the target code corresponding to the first requester account.
5. The method of claim 4, wherein reclaiming the processing right of the object code by the second requester account associated with the subtask single number comprises:
setting the recovery time for recovering the processing authority of the second requester account related to the subtask single number;
recording the submission time after submitting the coded corresponding to the subtask single number;
and recovering the processing permission of the second applicant account related to the subtask single number under the condition that the submission time exceeds the recovery time.
6. The method of claim 1, further comprising:
receiving a predetermined plan sent by a first applicant account, wherein the predetermined plan comprises a predetermined time period and a predetermined task list, and the predetermined task list comprises information of a target code and information of processing authority required by the target code;
sending the predetermined plan to an approver;
and under the condition that an instruction that the approving party agrees to the predetermined plan is received, the processing permission required by the target code in the predetermined task list is granted to the first requester account in the predetermined time period.
7. An apparatus for controlling authority of a task, comprising:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is configured to receive a task sheet sent by a first applicant account, the task sheet comprises at least one subtask sheet, and the subtask sheet comprises information of a target code and information of processing authority required by the target code;
the sending module is configured to send the task list to an approver;
and the authorization module is configured to grant the processing permission required by the target code corresponding to each subtask sheet to the first applicant account respectively under the condition that the instruction that the first applicant account obtains the processing permission is received by the approval party.
8. The apparatus of claim 7, further comprising:
the first determination module is configured to determine a subtask sheet number based on a subtask sheet in a task sheet sent by a first requester account;
the association module is configured to associate the subtask single number with a first requester account with submission permission and store the subtask single number and the first requester account into a task table;
the second determination module is configured to receive a coded request corresponding to the subtask single number submitted by a second applicant account, and determine the first applicant account associated with the subtask single number in the task table according to the subtask single number;
the comparison module is configured to compare the second applicant account with the first applicant account determined in the task table;
and the recovery module is configured to submit the coded codes corresponding to the subtask single number and recover the processing permission of the second requester account related to the subtask single number to the target codes under the condition that the second requester account is the same as any one of the first requester accounts determined in the task table.
9. A computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, wherein the processor implements the steps of the method of any one of claims 1-6 when executing the instructions.
10. A computer-readable storage medium storing computer instructions, which when executed by a processor, perform the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911114769.5A CN110874219B (en) | 2019-11-14 | 2019-11-14 | Task permission control method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911114769.5A CN110874219B (en) | 2019-11-14 | 2019-11-14 | Task permission control method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110874219A true CN110874219A (en) | 2020-03-10 |
| CN110874219B CN110874219B (en) | 2023-05-09 |
Family
ID=69718128
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911114769.5A Active CN110874219B (en) | 2019-11-14 | 2019-11-14 | Task permission control method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110874219B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112215586A (en) * | 2020-11-17 | 2021-01-12 | 苏州易企慧创软件有限公司 | Project collaborative management method, system and storage medium based on task nodes |
| CN113114674A (en) * | 2021-04-12 | 2021-07-13 | 北京锐安科技有限公司 | Service access method, device, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103166911A (en) * | 2011-12-09 | 2013-06-19 | 阿里巴巴集团控股有限公司 | Version management server authority management method and version management server authority management equipment |
| CN106778345A (en) * | 2016-12-19 | 2017-05-31 | 网易（杭州）网络有限公司 | The treating method and apparatus of the data based on operating right |
| CN109976883A (en) * | 2017-12-27 | 2019-07-05 | 深圳市优必选科技有限公司 | A kind of processing method and its system of task |
| CN110096303A (en) * | 2019-04-22 | 2019-08-06 | 无线生活（杭州）信息科技有限公司 | Code detection method and device |
| US20190339966A1 (en) * | 2018-05-06 | 2019-11-07 | Methodics, Inc. | Component design security through restriction of a design component dependency tree |
-
2019
- 2019-11-14 CN CN201911114769.5A patent/CN110874219B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103166911A (en) * | 2011-12-09 | 2013-06-19 | 阿里巴巴集团控股有限公司 | Version management server authority management method and version management server authority management equipment |
| CN106778345A (en) * | 2016-12-19 | 2017-05-31 | 网易（杭州）网络有限公司 | The treating method and apparatus of the data based on operating right |
| CN109976883A (en) * | 2017-12-27 | 2019-07-05 | 深圳市优必选科技有限公司 | A kind of processing method and its system of task |
| US20190339966A1 (en) * | 2018-05-06 | 2019-11-07 | Methodics, Inc. | Component design security through restriction of a design component dependency tree |
| CN110096303A (en) * | 2019-04-22 | 2019-08-06 | 无线生活（杭州）信息科技有限公司 | Code detection method and device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112215586A (en) * | 2020-11-17 | 2021-01-12 | 苏州易企慧创软件有限公司 | Project collaborative management method, system and storage medium based on task nodes |
| CN113114674A (en) * | 2021-04-12 | 2021-07-13 | 北京锐安科技有限公司 | Service access method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110874219B (en) | 2023-05-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11386405B2 (en) | Dynamic blockchain transactional policy management | |
| US20150378722A1 (en) | Enhanced compliance verification system | |
| CN109726099A (en) | A kind of application gray scale dissemination method, device and equipment | |
| US20150207821A1 (en) | System and method for resolving conflicts between application control rules | |
| KR101876674B1 (en) | Method of managing common account using block chain and system performing the same | |
| CN102404136A (en) | Methods and apparatus associated with dynamic access control based on a task/trouble ticket | |
| CN110909373A (en) | Access control method, device, system and storage medium | |
| CN110874219B (en) | Task permission control method and device | |
| CN110213290A (en) | Data capture method, API gateway and storage medium | |
| JP2023543596A (en) | Systems and methods for processing customer data | |
| WO2024002103A1 (en) | Data asset management method and data asset active management system | |
| CN102750604A (en) | Apparatus and methods for activity-based management of computer systems | |
| CN109087065A (en) | Intelligent device management method and system | |
| CN107832590A (en) | Terminal control method and device, terminal and computer-readable recording medium | |
| US11405381B2 (en) | Tag-based access permissions for cloud computing resources | |
| CN116107715B (en) | Method for running Docker container task and task scheduler | |
| CN111435495B (en) | Service processing method, device and equipment | |
| CN115328053B (en) | Permission realization method based on security level DCS system of nuclear power plant | |
| CN111026569A (en) | Method for repairing designated block data in alliance chain | |
| US20230073235A1 (en) | Method and apparatus for performing horizontal federated learning | |
| CN115001776B (en) | Data processing system and method | |
| CN110555682A (en) | multi-channel implementation method based on alliance chain | |
| CN111291065B (en) | Asset data modification method and device executed by computing equipment and computing equipment | |
| CN114915453A (en) | Access response method and device | |
| CN114676104A (en) | Log generation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 519000 room 402, Room 401, No. 327, Qiandao Ring Road, Tangjiawan Town, high tech Zone, Zhuhai City, Guangdong Province Applicant after: Zhuhai Xishanju Digital Technology Co.,Ltd. Address before: 519000 room 402, Room 401, No. 327, Qiandao Ring Road, Tangjiawan Town, high tech Zone, Zhuhai City, Guangdong Province Applicant before: ZHUHAI SEASUN MOBILE GAME TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |