CN117874727A - Request processing method, request processing device, electronic equipment and storage medium - Google Patents
Request processing method, request processing device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN117874727A CN117874727A CN202311778760.0A CN202311778760A CN117874727A CN 117874727 A CN117874727 A CN 117874727A CN 202311778760 A CN202311778760 A CN 202311778760A CN 117874727 A CN117874727 A CN 117874727A
- Authority
- CN
- China
- Prior art keywords
- user
- data
- service system
- grade
- application entity
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 26
- 238000012545 processing Methods 0.000 title claims abstract description 17
- 238000013523 data management Methods 0.000 claims abstract description 69
- 238000000034 method Methods 0.000 claims abstract description 32
- 238000004590 computer program Methods 0.000 claims description 13
- 238000007726 management method Methods 0.000 description 27
- 238000010586 diagram Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000007792 addition Methods 0.000 description 3
- 238000013475 authorization Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000002955 isolation Methods 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Landscapes
- Storage Device Security (AREA)
Abstract
The application discloses a request processing method, a request processing device, electronic equipment and a storage medium, wherein the method comprises the following steps: receiving a first request sent by a first user to acquire a first data management authority for managing first data, wherein the first request comprises a first login account of the first user on a first service system; the first user is a registered user on the first service system; determining a first user grade of the first user on the first service system based on the first login account; and under the condition that the first user grade meets the first preset condition, issuing first data management authority to the first user so that the first user manages the first data on the first service system by using the first data management authority. According to the embodiment of the application, the workload of a system administrator can be reduced, and the data management efficiency is improved.
Description
Technical Field
The application belongs to the technical field of data management, and particularly relates to a request processing method, a request processing device, electronic equipment and a storage medium.
Background
Currently, system data management (including addition, deletion, and modification of data) on most business systems is uniformly managed by a system administrator.
Therefore, once the system data needs to be added, deleted or modified, the system administrator needs to be notified to process, which results in a large workload of the system administrator, and the number of the system administrators of a service system is usually small, and a phenomenon that the system administrator cannot manage the data on demand in time may occur, which results in a low system data management efficiency.
Disclosure of Invention
The embodiment of the application provides a request processing method, a request processing device, electronic equipment and a storage medium, which can solve the problem of low system data management efficiency.
In one aspect, an embodiment of the present application provides a request processing method, applied to a first electronic device, where the method includes:
receiving a first request sent by a first user to acquire a first data management authority for managing first data, wherein the first request comprises a first login account of the first user on a first service system; the first user is a registered user on the first service system;
determining a first user grade of the first user on the first service system based on the first login account;
and under the condition that the first user grade meets the first preset condition, issuing first data management authority to the first user so that the first user manages the first data on the first service system by using the first data management authority.
In another aspect, an embodiment of the present application provides a request processing apparatus, including:
the first receiving module is used for receiving a first request for acquiring a first data management authority for managing first data sent by a first user, wherein the first request comprises a first login account of the first user on a first service system; the first user is a registered user on the first service system;
the first determining module is used for determining a first user grade of a first user on a first service system based on the first login account;
the issuing module is used for issuing first data management authority to the first user under the condition that the first user grade meets a first preset condition, so that the first user manages first data on the first service system by using the first data management authority.
In yet another aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory storing computer program instructions;
the above-described request processing method is implemented when the processor executes the computer program instructions.
In yet another aspect, embodiments of the present application provide a computer readable storage medium having stored thereon computer program instructions that when executed by a processor implement the above-described request processing method.
The request processing method, the request processing device, the electronic equipment and the storage medium can receive a first request sent by a first user to acquire first data management authority for managing first data, determine a first user grade of the first user on a first service system based on a first login account, and issue the first data management authority to the first user under the condition that the first user grade meets a first preset condition so that the first user manages the first data on the first service system by using the first data management authority. Therefore, when the first user does not have the management data authority, the request for acquiring the data management authority can be sent, and when the user level of the first user is determined to meet the condition, the data management authority is issued, so that the first user can manage the data without a system administrator. Therefore, the workload of a system administrator is reduced, and the data management efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described, and it is possible for a person skilled in the art to obtain other drawings according to these drawings without inventive effort.
FIG. 1 is a flow chart of a request processing method according to an embodiment of the present application;
FIG. 2 is a flow chart of a request processing method according to another embodiment of the present application;
FIG. 3 is a flow chart of a request processing method according to another embodiment of the present application;
FIG. 4 is a flow chart of a request processing method according to another embodiment of the present application;
FIG. 5 is a flow chart of a request processing method according to another embodiment of the present application;
FIG. 6 is a schematic diagram of a request processing apparatus according to an embodiment of the present application;
fig. 7 is a schematic hardware structure of an electronic device according to an embodiment of the present application.
Detailed Description
Features and exemplary embodiments of various aspects of the present application are described in detail below to make the objects, technical solutions and advantages of the present application more apparent, and to further describe the present application in conjunction with the accompanying drawings and the detailed embodiments. It should be understood that the specific embodiments described herein are intended to be illustrative of the application and are not intended to be limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by showing examples of the present application.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
In order to solve the problems in the prior art, the embodiments of the present application provide a request processing method, a device, an electronic device, and a storage medium, and the request processing method provided in the embodiments of the present application is first described below.
Fig. 1 shows a flow chart of a request processing method according to an embodiment of the present application, as shown in fig. 1, the method includes the following flow chart:
step 101: receiving a first request sent by a first user to acquire a first data management authority for managing first data, wherein the first request comprises a first login account of the first user on a first service system; the first user is a registered user on the first business system.
In some embodiments, the first service system may integrate Account (Account) management, authentication (Authentication) management, authorization (Authorization) management and security Audit (audio) in the service support system into a centralized and unified security service system, referred to as a 4A management platform or a 4A system. The login account numbers on the user and the first service system are in one-to-one correspondence, namely: a user corresponds to a login account on the first service system, and after the user registers on the first service system, the user can have a login account and can manage part or all of the data in the first service system. In one example, when a user wants to obtain rights to manage part or all of the data in the first business system, a data management rights request may be sent to the system, where the request includes a login account used when the user logs into the first business system.
Step 102: a first user rating of the first user on the first business system is determined based on the first login account.
In some embodiments, the first login account may carry user basic information, for example: the user name, the user's management level at the company, etc., the first user level of the user on the first business system may be determined by the first login account. In an example, assuming that the user is a department manager, the login account of the user carries related information, which indicates that the owner of the login account is a certain department manager, and finds a corresponding user level on the first service system based on the identity of the department manager.
Step 103: and under the condition that the first user grade meets the first preset condition, issuing first data management authority to the first user so that the first user manages the first data on the first service system by using the first data management authority.
In some embodiments, when the user level meets the first preset condition, a data management authority corresponding to the user level of the user may be issued to the login account of the user, and the user manages part or all of the data in the first service system through the data management authority. The user grade and the data management authority corresponding to the user grade are preset before the user applies for the data management authority, if the data management authority corresponding to the user grade of the user can not be found, the user can not apply for the data management authority, namely: the user fails to apply for the data management authority. And the data management authority corresponding to the preset user level can be stored and managed, and when the user applies for the data management authority, the data management authority corresponding to the user level can be found from the stored data management authority.
In the embodiment of the application, a first request for acquiring a first data management authority for managing first data sent by a first user can be received, a first user grade of the first user on a first service system is determined based on a first login account, and the first data management authority is issued to the first user under the condition that the first user grade meets a first preset condition, so that the first user manages the first data on the first service system by using the first data management authority. Therefore, when the first user does not have the management data authority, the request for acquiring the data management authority can be sent, and when the user level of the first user is determined to meet the condition, the data management authority is issued, so that the first user can manage the data without a system administrator. Therefore, the workload of a system administrator is reduced, and the data management efficiency is improved.
Fig. 2 is a flow chart illustrating a request processing method according to another embodiment of the present application, where, as shown in fig. 2, the first user level includes a first role level of a first application entity to which the first user belongs on the first service system, and before step 103, the method further includes:
step 201: determining an application entity to which the first data belongs;
step 202: and under the condition that the application entity to which the first data belongs is a first application entity and the first role grade is the manager role of the first application entity, determining that the first user grade meets a first preset condition.
In some embodiments, the application entity may be a 4A system, and in the case where the application entity is a 4A system, the first user may be a system administrator, and the system administrator may manage any data in the entire 4A system, where the administrator role is built in by the 4A system, and there is only one. As an example, when a user is managing all data in a 4A system, namely: the first data are all data in the 4A system, whether the user is a system administrator of the 4A system is determined, if so, the user can be issued with the authority for managing all data in the 4A system, so that the user can manage all data in the 4A system by using the authority, and if not, the user fails to apply for the data management authority.
In other embodiments, the application entity may be an account management subsystem in the 4A system, and in the case that the application entity is the account management subsystem in the 4A system, the first user may be an enterprise administrator, and the enterprise administrator may manage an organization management of the enterprise and a personnel management of the enterprise through the account management subsystem. Each enterprise has and only one enterprise administrator role, the enterprise is created by the system administrator of the 4A system, and the enterprise administrator automatically creates when the system administrator creates the enterprise. In one example, when a user is managing all data in a business, namely: the first data are all data of a certain enterprise, whether the user is an enterprise administrator of the certain enterprise is determined, if yes, the user can be issued with the authority for managing all data of the certain enterprise, so that the user can manage all data of the certain enterprise by using the authority, and if not, the user fails to apply for the data management authority. The 4A system and the enterprise are one-to-many relationship, that is, a plurality of enterprises can be set and managed in one 4A system, and the user and the enterprise are one-to-many relationship, that is, a plurality of enterprises can be managed in one user.
In other embodiments, the application entity may be a rights management subsystem in a 4A system. In the case that the application entity is a rights management subsystem in the 4A system, the first user may be an application manager, which may manage functional rights management of the application and data rights management of the application through the rights management subsystem. Each application has and only has one application manager role, the application is then created by the system manager of the 4A system or the enterprise manager of a certain enterprise, and the application manager will automatically create when the system manager or the enterprise manager creates the application. In one example, when a user is managing all data in a certain application, namely: the first data is all data of a certain application, whether the user is an application manager of the certain application is determined, if so, the user can be issued with the authority for managing all data of the certain application, so that the user can manage all data of the certain application by using the authority, and if not, the user fails to apply for the data management authority. The 4A system and the application are one-to-many relationship, that is, a plurality of applications can be set and managed in one 4A system, the enterprise and the application are one-to-many relationship, that is, a plurality of applications can be set and managed in one enterprise, and the user and the application are one-to-many relationship, that is, a plurality of applications can be managed in one user.
In some embodiments, the application entity may be a 4A system, and in the case where the application entity is a 4A system, the first user may be a sub-administrator of the 4A system, the sub-administrator being different from a system administrator of the 4A system, namely: the scope of the functional rights and data rights that can be managed by the sub-administrator is different from that of the system administrator. The sub-administrator can only modify passwords in the 4A system, modify some information that the person itself can modify, query log-in, query log-operation, etc., or another function is to query authorization (function rights and data rights) information for a certain application through the 4A system.
It can be appreciated that in this embodiment, by determining the application entity corresponding to the user and the manager role in the application entity, it is determined whether the data management authority applied by the user accords with the data management authority corresponding to the user level, and by dividing the data and the authority in the service system from different enterprises and different applications, a data boundary is formed between different enterprises and different applications, and data isolation between different enterprises and different applications is achieved.
Fig. 3 is a flow chart illustrating a request processing method according to another embodiment of the present application, as shown in fig. 3, where the method further includes:
step 301: receiving a second request for the second user to send second data, wherein the second request comprises a second login account of the second user on the first service system;
step 302: determining a second user grade of the second user on the first service system according to the second login account;
step 303: and allowing the second user to manage the second data under the condition that the second user level meets the second preset condition.
In this embodiment, after the user applies for the data management authority, and the application is successful, the data corresponding to the data management authority may be managed, and in the process of managing the data, a request corresponding to the management data sent by the user will be received, where the request includes a login account of the user, and personal information of the user, such as a user name, a user management account authority, and the like, may be carried in the login account.
It can be understood that by verifying the user grade corresponding to the login account in the request corresponding to the management data sent by the user, the user is prevented from managing data beyond the data management authority corresponding to the user grade, and the security of the data is ensured.
Fig. 4 is a flow chart illustrating a request processing method according to another embodiment of the present application, where, as shown in fig. 4, the second user level includes a second role level of a second application entity to which the second user belongs on the first service system, and before step 303, the method further includes:
step 401: determining an application entity to which the second data belongs;
step 402: and under the condition that the application entity to which the second data belongs is a second application entity and the second role level is the manager role of the second application entity, determining that the second user level meets a second preset condition.
In some embodiments, the application entity may be a 4A system, and in the case where the application entity is a 4A system, the second user may be a system administrator. When the second data are all data in the 4A system, whether the user grade corresponding to the login account is the grade of a system administrator or not can be determined through the login account of the second user, when the user grade corresponding to the login account is the grade of the system administrator, the second user can manage all data in the 4A system, and if the user grade corresponding to the login account is not the grade of the system administrator, all data in the 4A system cannot be managed.
In other embodiments, the application entity may be an account management subsystem in the 4A system, and the second user may be an enterprise administrator in the case where the application entity is an account management subsystem in the 4A system. When the second data is all data of a certain enterprise, whether the user grade corresponding to the login account is the grade of an enterprise manager of the certain enterprise or not can be determined through the login account of the second user, when the user grade corresponding to the login account is the grade of the enterprise manager of the certain enterprise, the second user can manage all the data of the enterprise, and if the user grade corresponding to the login account is not the grade of the enterprise manager of the certain enterprise, all the data in the enterprise cannot be managed.
In other embodiments, the application entity may be a rights management subsystem in the 4A system, and the second user may be an application administrator in the case where the application entity is a rights management subsystem in the 4A system. When the second data is all data of a certain application, whether the user grade corresponding to the login account is the grade of an application manager of the certain application or not can be determined through the login account of the second user, when the user grade corresponding to the login account is the grade of the application manager of the certain application, the second user can manage all data of the application, and if the user grade corresponding to the login account is not the grade of the application manager of the certain application, all data in the application cannot be managed.
In other embodiments, the application entity may be a 4A system, and in the case where the application entity is a 4A system, the second user may be a sub-administrator. When the second data is part of the data and the authority in the 4A system, whether the user grade corresponding to the login account is the grade of the sub-manager or not can be determined through the login account of the second user, when the user grade corresponding to the login account is the grade of the sub-manager, the second user can manage the part of the data and the authority in the 4A system, and if the user grade corresponding to the login account is not the grade of the sub-manager, the part of the data and the authority in the 4A system cannot be managed.
It can be understood that in the above embodiment, each user can only manage the data under the application entity itself, but cannot manage the data of other application entities, so as to realize data isolation and further improve the security of the data.
Fig. 5 shows a flowchart of a request processing method according to another embodiment of the present application, as shown in fig. 5, step 303 includes any one of the following:
step 501: when the second data is newly added data, allowing the second user to newly add the second data to the corresponding position in the first service system;
step 502: and when the second data is the data existing on the first service system, allowing the second user to modify or delete the second data.
In this embodiment, in the case where the user level satisfies the second preset condition, the data in the data management authority corresponding to the user level may be managed, where the management includes adding data, deleting data, modifying data, and searching data. In an example, where the first business system is an account management subsystem in the 4A system and the user is an enterprise administrator, the enterprise administrator may add enterprise personnel of the managed enterprise, delete enterprise personnel of the managed enterprise, modify personnel information of enterprise personnel of the managed enterprise, query enterprise personnel of the managed enterprise, and so on.
It will be appreciated that in this embodiment, each user may manage data under its own application entity, and implement addition of data, deletion of data, modification of data, and lookup of data, thereby implementing data management.
It should be noted that, the various optional embodiments described in the embodiments of the present application may be implemented in combination with each other without collision, or may be implemented separately, which is not limited to the embodiments of the present application.
Fig. 6 is a schematic structural diagram of a request processing apparatus according to an embodiment of the present application, as shown in fig. 6, where the apparatus includes:
the first receiving module 601 is configured to receive a first request sent by a first user to obtain a first data management right for managing first data, where the first request includes a first login account of the first user on a first service system; the first user is a registered user on the first service system;
a first determining module 602, configured to determine a first user level of the first user on the first service system based on the first login account;
and the issuing module 603 is configured to issue a first data management right to the first user if the first user level meets a first preset condition, so that the first user manages the first data on the first service system by using the first data management right.
In this embodiment, the first receiving module 601 receives a first request sent by the first user to obtain a first data management right for managing the first data, the first determining module 602 determines, based on the first login account, a first user level of the first user on the first service system, and the issuing module 603 issues the first data management right to the first user when the first user level meets a first preset condition, so that the first user manages the first data on the first service system by using the first data management right. Therefore, when the first user does not have the management data authority, the request for acquiring the data management authority can be sent, and when the user level of the first user is determined to meet the condition, the data management authority is issued, so that the first user can manage the data without a system administrator. Therefore, the workload of a system administrator is reduced, and the data management efficiency is improved.
As an alternative embodiment, the first user class includes a first role class of a first application entity to which the first user belongs on the first service system, and the request processing apparatus may further include:
the second determining module is used for determining an application entity to which the first data belongs before issuing the first data management authority to the first user under the condition that the first user grade meets a first preset condition;
and the third determining module is used for determining that the first user grade meets a first preset condition under the condition that the application entity to which the first data belongs is a first application entity and the first role grade is a manager role of the first application entity.
As an alternative embodiment, the request processing apparatus may further include:
the second receiving module is used for receiving a second request for managing second data sent by a second user, wherein the second request comprises a second login account of the second user on the first service system;
the fourth determining module is used for determining a second user grade of the second user on the first service system according to the second login account;
and the permission module is used for permitting the second user to manage the second data under the condition that the second user level meets the second preset condition.
As an alternative embodiment, the second user class includes a second role class of a second application entity to which the second user belongs on the first service system, and the request processing apparatus may further include:
a fifth determining module, configured to determine an application entity to which the second data belongs before allowing the second user to manage the second data if the second user level meets a second preset condition;
and the sixth determining module is used for determining that the second user grade meets a second preset condition when the application entity to which the second data belongs is a second application entity and the second role grade is a manager role of the second application entity.
As an alternative embodiment, the permission module may further include any one of the following:
when the second data is newly added data, allowing the second user to newly add the second data to the corresponding position in the first service system;
and when the second data is the data existing on the first service system, allowing the second user to modify or delete the second data.
Fig. 7 shows a schematic hardware structure of an electronic device according to an embodiment of the present application.
A processor 701 may be included in an electronic device, as well as a memory 702 in which computer program instructions are stored.
In particular, the processor 701 described above may include a Central Processing Unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of embodiments of the present application.
Memory 702 may include mass storage for data or instructions. By way of example, and not limitation, memory 702 may comprise a Hard Disk Drive (HDD), floppy Disk Drive, flash memory, optical Disk, magneto-optical Disk, magnetic tape, or universal serial bus (Universal Serial Bus, USB) Drive, or a combination of two or more of the foregoing. The memory 702 may include removable or non-removable (or fixed) media, where appropriate. Memory 702 may be internal or external to the integrated gateway disaster recovery device, where appropriate. In a particular embodiment, the memory 702 is a non-volatile solid state memory.
The memory may include Read Only Memory (ROM), random Access Memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform the operations described with reference to methods in accordance with aspects of the present disclosure.
The processor 701 implements any of the request processing methods of the above embodiments by reading and executing computer program instructions stored in the memory 702.
In one example, the electronic device may also include a communication interface 703 and a bus 710. As shown in fig. 7, the processor 701, the memory 702, and the communication interface 703 are connected by a bus 710 and perform communication with each other.
The communication interface 703 is mainly used for implementing communication between each module, device, unit and/or apparatus in the embodiments of the present application.
Bus 710 includes hardware, software, or both that couple components of the electronic device to one another. By way of example, and not limitation, the buses may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a micro channel architecture (MCa) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics standards association local (VLB) bus, or other suitable bus, or a combination of two or more of the above. Bus 710 may include one or more buses, where appropriate. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.
In addition, in combination with the request processing method in the above embodiment, the embodiment of the application may be implemented by providing a computer readable storage medium. The computer readable storage medium has stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement any of the request processing methods of the above embodiments.
It should be clear that the present application is not limited to the particular arrangements and processes described above and illustrated in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications, and additions, or change the order between steps, after appreciating the spirit of the present application.
The functional blocks shown in the above block diagrams may be implemented in hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the present application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transfer information. Examples of machine-readable media include electronic circuitry, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and the like. The code segments may be downloaded via computer networks such as the internet, intranets, etc.
It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be different from the order in the embodiments, or several steps may be performed simultaneously.
Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In the foregoing, only the specific embodiments of the present application are described, and it will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to the corresponding processes in the foregoing method embodiments, which are not repeated herein. It should be understood that the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present application, which are intended to be included in the scope of the present application.
Claims (10)
1. A method for processing a request, applied to a first electronic device, comprising:
receiving a first request of a first user for acquiring a first data management authority for managing first data, wherein the first request comprises a first login account of the first user on a first service system; the first user is a registered user on the first service system;
determining a first user grade of the first user on a first service system based on the first login account;
and under the condition that the first user grade meets a first preset condition, issuing the first data management authority to the first user so that the first user manages the first data on the first service system by using the first data management authority.
2. The method of claim 1, wherein the first user level comprises a first role level of a first application entity to which the first user belongs on the first business system, and wherein the method further comprises, prior to issuing the first data management right to the first user if the first user level satisfies a first preset condition:
determining an application entity to which the first data belongs;
and under the condition that the application entity to which the first data belongs is a first application entity and the first role grade is a manager role of the first application entity, determining that the first user grade meets a first preset condition.
3. The method according to claim 1, wherein the method further comprises:
receiving a second request of a second user for managing second data, wherein the second request comprises a second login account of the second user on the first service system;
determining a second user grade of the second user on the first service system according to the second login account;
and allowing the second user to manage the second data under the condition that the second user level meets a second preset condition.
4. A method according to claim 3, wherein the second user class comprises a second role class of a second application entity to which the second user belongs on the first business system, and wherein the method further comprises, before allowing the second user to manage the second data if the second user class meets a second preset condition:
determining an application entity to which the second data belongs;
and under the condition that the application entity to which the second data belongs is a second application entity and the second role grade is the manager role of the second application entity, determining that the second user grade meets a second preset condition.
5. The method of claim 4, wherein the allowing the second user to manage the second data comprises any one of:
when the second data is newly added data, allowing the second user to newly add the second data to a corresponding position in the first service system;
and when the second data is the data existing on the first service system, allowing the second user to modify or delete the second data.
6. A request processing apparatus, comprising:
the first receiving module is used for receiving a first request for acquiring a first data management authority for managing first data, wherein the first request comprises a first login account of the first user on a first service system; the first user is a registered user on the first service system;
the first determining module is used for determining a first user grade of the first user on a first service system based on the first login account;
and the issuing module is used for issuing the first data management authority to the first user under the condition that the first user grade meets a first preset condition so that the first user can manage the first data on the first service system by using the first data management authority.
7. The apparatus of claim 6, wherein the first user level comprises a first persona level of a first application entity to which the first user belongs on the first business system, the apparatus further comprising:
the second determining module is used for determining an application entity to which the first data belongs before issuing the first data management authority to the first user under the condition that the first user grade meets a first preset condition;
and the third determining module is used for determining that the first user grade meets a first preset condition under the condition that the application entity to which the first data belongs is a first application entity and the first role grade is a manager role of the first application entity.
8. The apparatus of claim 7, wherein the apparatus further comprises:
the second receiving module is used for receiving a second request for managing second data sent by a second user, wherein the second request comprises a second login account of the second user on the first service system;
a fourth determining module, configured to determine, according to the second login account id, a second user level of the second user on the first service system;
and the permission module is used for permitting the second user to manage the second data under the condition that the second user level meets a second preset condition.
9. An electronic device, the device comprising: a processor and a memory storing computer program instructions;
the processor, when executing the computer program instructions, implements a request processing method as claimed in any one of claims 1-5.
10. A computer readable storage medium, wherein computer program instructions are stored on the computer readable storage medium, which when executed by a processor, implement the request processing method according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311778760.0A CN117874727A (en) | 2023-12-22 | 2023-12-22 | Request processing method, request processing device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311778760.0A CN117874727A (en) | 2023-12-22 | 2023-12-22 | Request processing method, request processing device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117874727A true CN117874727A (en) | 2024-04-12 |
Family
ID=90593869
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311778760.0A Pending CN117874727A (en) | 2023-12-22 | 2023-12-22 | Request processing method, request processing device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117874727A (en) |
-
2023
- 2023-12-22 CN CN202311778760.0A patent/CN117874727A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104364790B (en) | System and method for implementing dual factor anthentication | |
| CN109361718B (en) | Identity authentication method, apparatus and medium | |
| US10158626B1 (en) | Token-based access control | |
| CN109660346B (en) | Information hosting method, device, equipment and computer storage medium | |
| CN105453102A (en) | Systems and methods for identifying private keys that have been compromised | |
| CN110545272B (en) | Identity authentication method, authority authentication method, device, user management system and storage medium | |
| CN113852639B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN110855441B (en) | Method, device and equipment for authenticating electronic identity and storage medium | |
| CN116708576A (en) | Service providing method, device, equipment and computer readable storage medium | |
| CN117874727A (en) | Request processing method, request processing device, electronic equipment and storage medium | |
| CN115499487B (en) | Updating method and device of server configuration file, storage medium and equipment | |
| CN110955921A (en) | Electronic signature method, device, equipment and storage medium | |
| CN113542238B (en) | Zero trust-based risk judging method and system | |
| CN114372072A (en) | Data storage method, device, equipment, computer storage medium and program product | |
| US10748364B1 (en) | Methods and systems for access control | |
| CN110427747B (en) | Identity authentication method and device supporting service security mark | |
| CN109683942B (en) | Script management method, script management device, script management medium and electronic equipment | |
| KR102209481B1 (en) | Method for operating account reinstating service based account key pairs, system and computer-readable medium recording the method | |
| CN114553586A (en) | Data acquisition method, apparatus, device, medium, and program product | |
| CN111294315B (en) | Block chain-based security authentication method, block chain-based security authentication device, block chain-based security authentication equipment and storage medium | |
| CN114710450B (en) | Flow control method, device, equipment and computer storage medium | |
| CN116305246A (en) | Data processing method, apparatus, device, storage medium, and program product | |
| US11588684B2 (en) | Device provisioning using dedicated credential storage | |
| CN116016495A (en) | File downloading method, device, equipment, storage medium and product | |
| CN107133505B (en) | Authority management method, authentication method and system |
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 |