System account authority management method and device, electronic equipment and storage medium
Through the system account permission management method that works collaboratively between the client and the server, the complex and inefficient account permission management in the existing technology is solved, and the convenience and accuracy of account permission application is achieved.
Patent Information
- Application Number
- CN202510280026.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-10
- Publication Date
- 2025-06-10
AI Technical Summary
In the prior art, account permission management is complex, with low authenticity and accuracy, and high manual operation workload, resulting in low management efficiency.
Through the system account permission management method that works collaboratively between the client and the server, when users apply for account permissions, they automatically complete the permission configuration and approval process by obtaining identity information and selecting the target position identification.
It improves the efficiency of account permission application, reduces the workload and probability of errors in manual operations, and enhances the accuracy and authenticity of permission management.
Smart Images
Figure CN120124029A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of data processing, and particularly to a method, apparatus, electronic device, and storage medium for managing system account permissions. Background Art
[0002] In the related art, institutions at all levels apply for, approve, and configure account permissions through different processes, emails, paper approvals, etc. For all approved applications, the user system administrator needs to select, grant, update, and adjust permissions one by one, which not only makes the management of related account permission applications extremely complex, with low authenticity and accuracy, but also results in a huge amount of overall manual operation work. Summary of the Invention
[0003] The present disclosure provides a method, apparatus, electronic device, storage medium, and computer program product for managing system account permissions, aiming to solve the technical problems in the related art to at least some extent.
[0004] In a first aspect of the embodiments of the present disclosure, a method for managing system account permissions is provided, which is executed by a client. The method includes: when receiving an account permission application request from a user, obtaining the user's identity information, where the account permission application request includes: account permission description information; determining, according to the account permission description information, the system identification information of the system to be applied for corresponding to the user, where the system to be applied for has corresponding candidate positions, and each candidate position has a corresponding candidate position identifier; receiving the user's operation instruction, and determining at least one target position identifier from the candidate position identifier information according to the operation instruction; and sending the user's identity information and the target position identifier to the server.
[0005] In a second aspect of the embodiments of the present disclosure, a method for managing system account permissions is provided, which is characterized in that it is executed by the server. The method includes: receiving the user's identity information and the target position identifier sent by the client; approving the target position identifier according to the identity information to obtain a first approval result; when the first approval result is: approved, configuring the account permission information corresponding to the target position identifier for the user; and sending the account permission information corresponding to the target position identifier to the client.
[0006] Embodiments of the third aspect of the present disclosure provide a system account permission management device, which is executed by a client. The device includes: a first receiving module, configured to obtain the identity information of a user when receiving an account permission application request from the user, where the account permission application request includes: account permission description information; a determination module, configured to determine the system identification information of the system to be applied for corresponding to the user according to the account permission description information, where the system to be applied for has corresponding candidate positions, and each candidate position has a corresponding candidate position identifier; a second receiving module, configured to receive an operation instruction from the user and determine at least one target position identifier from the candidate position identifier information according to the operation instruction; a first sending module, configured to send the identity information of the user and the target position identifier to a server.
[0007] Embodiments of the fourth aspect of the present disclosure provide a system account permission management device, which is characterized in that it is executed by a server. The device includes: a third receiving module, configured to receive the identity information of the user and the target position identifier sent by the client; an approval module, configured to approve the target position identifier according to the identity information to obtain a first approval result; a configuration module, configured to configure the account permission information corresponding to the target position identifier for the user when the first approval result is: approval passed; a second sending module, configured to send the account permission information corresponding to the target position identifier to the client.
[0008] Embodiments of the fifth aspect of the present disclosure provide an electronic device, including: a processor; a memory for storing instructions executable by the processor; wherein, the processor is configured to execute the instructions to implement the system account permission management method according to the embodiments of the first aspect of the present disclosure, or implement the system account permission management method according to the embodiments of the second aspect of the present disclosure.
[0009] Embodiments of the sixth aspect of the present disclosure provide a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by the processor of the electronic device, enabling the electronic device to implement the system account permission management method according to the embodiments of the first aspect of the present disclosure, or implement the system account permission management method according to the embodiments of the second aspect of the present disclosure.
[0010] Embodiments of the seventh aspect of the present disclosure provide a computer program product, including a computer program, which is characterized in that the computer program is executed by the processor to implement the system account permission management method according to the embodiments of the first aspect of the present disclosure, or implement the system account permission management method according to the embodiments of the second aspect of the present disclosure.
[0011] The system account permission management method, device, electronic device, storage medium, and computer program product proposed in this embodiment at least have the following beneficial effects: When the client receives a user's account permission application request, it obtains the user's identity information. Among them, the account permission application request includes: account permission description information. According to the account permission description information, it determines the system identification information of the system to be applied for corresponding to the user. Among them, the system to be applied for has corresponding candidate positions, and each candidate position has a corresponding candidate position identifier. It receives the user's operation instruction, and determines at least one target position identifier from the candidate position identifier information according to the operation instruction, and sends the user's identity information and the target position identifier to the server. Thus, it supports the user to conveniently select the position permissions and position permission combinations of multiple systems when applying for account permissions, thereby effectively improving the efficiency of account permission applications.
[0012] Additional aspects and advantages of the present disclosure will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The above and / or additional aspects and advantages of the present disclosure will become apparent and be readily understood from the following description of the embodiments in conjunction with the drawings, where:
[0014] Figure 1 is a flowchart of a system account permission management method shown according to the first embodiment of the present disclosure;
[0015] Figure 2 is a flowchart of a system account permission management method shown according to the second embodiment of the present disclosure;
[0016] Figure 3 is a flowchart of a system account permission management method shown according to the present disclosure;
[0017] Figure 4 is a block diagram of a system account permission management device shown according to the present disclosure;
[0018] Figure 5 is a block diagram of a system account permission management device shown according to the present disclosure;
[0019] Figure 6 shows a block diagram of an exemplary electronic device suitable for implementing the embodiments of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0020] Embodiments of the present disclosure will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where like or similar reference numerals denote like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the accompanying drawings are exemplary and are only used to explain the present disclosure and should not be construed as a limitation of the present disclosure. On the contrary, the embodiments of the present disclosure include all changes, modifications, and equivalents falling within the spirit and scope of the appended claims.
[0021] It should be noted that the execution subject of the system account permission management method in this embodiment may be a first server, and the first server may be configured in an electronic device, and the electronic device may include, but is not limited to, a terminal, a server, etc.
[0022] It should be noted that in the technical solution of the present disclosure, the processes of obtaining, storing, using, processing, etc. of information all comply with the relevant regulations of national laws and regulations and do not violate public order and good customs.
[0023] It should be noted that in the embodiments of the present application, there may be existing solutions in the industry for certain software, components, models, etc. They should be regarded as exemplary. The purpose is only to illustrate the feasibility in the implementation of the technical solution of the present application, but it does not mean that the applicant has already or necessarily used the relevant content of this solution.
[0024] Figure 1 is a flowchart of the system account permission management method shown in the first embodiment of the present disclosure. As Figure 1 shown, it is executed by the client, and the method includes:
[0025] S101: When receiving an account permission application request from a user, obtain the user's identity information, where the account permission application request includes: account permission description information.
[0026] The user's account permission application request refers to a request made by the user to apply for the account usage permission of the corresponding position. The permission may be, for example, the system data query permission, the system data editing permission, etc., and is not limited thereto.
[0027] The user's identity information may be, for example, the user's name, the user's phone number, the user's ID number, the user's work number, etc., and is not limited thereto.
[0028] The account permission description information may include the system identifier, the position identifier, etc. applied for by the user's requirement. For example, the user requires to apply for the data editing permission of the core business system (position: underwriting preliminary review + report viewing), and is not limited thereto.
[0029] That is to say, in the embodiments of the present disclosure, the user can submit a system user account and permission application request on the client side. At the same time, the system supports finding the job number account information of the user applying for the account permission in the front-end personnel identity management system through an associated query method, and automatically synchronizing user information such as the user's name, user's phone number, user's ID number, and personnel category.
[0030] S102: Determine the system identification information of the system to be applied for corresponding to the user according to the account permission description information, where the system to be applied for has corresponding candidate positions, and each candidate position has a corresponding candidate position identifier.
[0031] Among them, the system identification information refers to the name and number of the system to be applied for, etc. The system to be applied for can be, for example, a claims settlement system, an underwriting system, a sales system, etc., and there is no limitation on this.
[0032] Among them, each system to be applied for corresponds to multiple candidate positions. The candidate position can be, for example, a survey and loss assessment position, a personal injury tracking position, etc., and there is no limitation on this.
[0033] In the embodiments of the present disclosure, when the client receives the user's account permission application request, it can automatically synchronize and display the candidate positions and combined positions corresponding to the system to be applied for, so as to support the user to determine the position to be applied for from the candidate positions corresponding to the system to be applied for displayed on the client. For details, please refer to the subsequent embodiments and will not be elaborated here.
[0034] S103: Receive the user's operation instruction, and determine at least one target position identifier from the candidate position identifier information according to the operation instruction.
[0035] Among them, the user's operation instruction refers to the instruction made by the user to determine the target position identifier from the multiple candidate position identifiers displayed on the client. The operation instruction can be, for example, the user's touch instruction, voice instruction, etc., and there is no limitation on this.
[0036] Among them, the target position identifier refers to the identifier information of the position selected by the user's requirement.
[0037] That is to say, in the embodiments of the present disclosure, the client can receive the user's operation instruction and determine at least one target position identifier from the candidate position identifier information in response to the user's operation instruction.
[0038] Optionally, in some embodiments, determining at least one target position identifier from the candidate position identifier according to the operation instruction can be to obtain and display a position identifier information configuration table preset for the system to be applied for, where the position identifier information configuration table includes: candidate position identifiers, and / or candidate position identifier groups, and then determine the target position identifier from the position identifier information configuration table according to the operation instruction.
[0039] Among them, the job identification information configuration table refers to a system with a large number of jobs. By pre-setting job permission combinations, it supports the quick selection of job combinations and related permission configurations. The job identification information configuration table can be as shown in Table 1 below:
[0040] Table 1
[0041]
[0042] That is to say, in the embodiments of the present disclosure, it may be to obtain and display the job identification information configuration table preset for the system to be applied, so as to support the user to efficiently determine a certain target job corresponding to the system to be applied that meets their needs, or a job combination corresponding to the system to be applied.
[0043] S104: Send the user's identity information and the target job identification to the server.
[0044] In the embodiments of the present disclosure, after receiving the user's operation instruction and determining at least one target job identification from the candidate job identification information, the user's identity information and the target job identification can be sent to the server, thereby triggering the automatic approval of the application process and the automatic authorization process of permissions.
[0045] Optionally, in the embodiments of the present disclosure, the account permission information corresponding to the target job identification sent by the server can also be received, and the account permission information can be verified to obtain a verification result.
[0046] Optionally, in some embodiments, when the verification result is: verification passed, the account permissions corresponding to the target job identification can be assigned to the user; when the verification result is: verification failed, an information indicating that the permission configuration fails can be generated.
[0047] Optionally, in some embodiments, after generating the information indicating that the permission configuration fails when the verification result is: verification failed, the information indicating that the permission configuration fails can be displayed, so as to support the user to modify the application process according to the information indicating that the permission configuration fails.
[0048] In the embodiments of the present disclosure, when the client receives a user's account permission application request, it obtains the user's identity information. The account permission application request includes account permission description information. According to the account permission description information, the system identification information of the system to be applied for corresponding to the user is determined. The system to be applied for has corresponding candidate positions, and each candidate position has a corresponding candidate position identifier. The client receives the user's operation instruction and determines at least one target position identifier from the candidate position identifier information, and then sends the user's identity information and the target position identifier to the server. Thus, when the user applies for account permissions, it supports the user to conveniently select the position permissions and position permission combinations of multiple systems, thereby effectively improving the efficiency of account permission application.
[0049] Figure 2 is a schematic flowchart of a system account permission management method shown in the second embodiment of the present disclosure. As Figure 2 shown, it is executed by the server. The method includes:
[0050] S201: Receive the user's identity information and the target position identifier sent by the client.
[0051] In the embodiments of the present disclosure, for the explanation of the same terms as those in the above embodiments, reference may specifically be made to the above embodiments and will not be elaborated herein.
[0052] That is to say, in the embodiments of the present disclosure, the server may receive the user's identity information and the target position identifier sent by the client.
[0053] S202: Approve the target position identifier according to the identity information to obtain a first approval result.
[0054] In the embodiments of the present disclosure, after receiving the user's identity information and the target position information sent by the client, the target position identifier may be approved according to the identity information to obtain a first approval result.
[0055] That is to say, in the embodiments of the present disclosure, the relevant departments and approvers of the server may approve the target position identifier according to the user's identity information to obtain a first approval result.
[0056] S203: When the first approval result is: approved, configure the account permission information corresponding to the target position identifier for the user.
[0057] In the embodiments of the present disclosure, after approving the target position identifier according to the identity information to obtain a first approval result, when the first approval result is: approved, the account permission information corresponding to the target position identifier may be configured for the user.
[0058] That is to say, in the embodiments of the present disclosure, when it is determined that the first approval result is approval, the target position selected by the user can be automatically authorized to configure account permission information corresponding to the target position identifier for the user.
[0059] S204: Send the account permission information corresponding to the target position identifier to the client.
[0060] In the embodiments of the present disclosure, after configuring the account permission information corresponding to the target position identifier for the user when the first approval result is approval, the account permission information corresponding to the target position identifier can be sent to the client.
[0061] In the embodiments of the present disclosure, the server receives the identity information of the user and the target position identifier sent by the client, then approves the target position identifier according to the identity information to obtain the first approval result. When the first approval result is approval, the account permission information corresponding to the target position identifier is configured for the user, and then the account permission information corresponding to the target position identifier is sent to the client. Thus, the account permission configurator can perform automatic authorization in the process, greatly improving the configuration efficiency on the basis of ensuring the accuracy of data, and reducing the workload and error probability of manual operations.
[0062] Figure 3 It is a flowchart of a system account permission management method shown according to the present disclosure, as Figure 3 shown: After the user submits the account permission application process, the user can independently select system positions and position combinations. After the system user account and permission application process are approved by relevant departments and approvers, it can be transferred to the account permission configurator. After the account permission configurator reviews the approval situation, through the "automatic authorization" operation, it can support batch pushing the position permission information of relevant personnel and the corresponding applied system to the user system at one key, and the user system automatically completes the position permission configuration.
[0063] Figure 4 It is a block diagram of a system account permission management device shown according to the present disclosure, as Figure 4 shown. The system account permission management device 40 is executed by the client. The device 40 includes:
[0064] The first receiving module 401 is used to obtain the identity information of the user when receiving the account permission application request of the user. Among them, the account permission application request includes: account permission description information;
[0065] The determination module 402 is used to determine the system identifier information of the system to be applied for corresponding to the user according to the account permission description information. Among them, the system to be applied for has corresponding candidate positions, and each candidate position has a corresponding candidate position identifier;
[0066] A second receiving module 403, configured to receive an operation instruction of a user, and determine at least one target position identifier from the candidate position identifier information according to the operation instruction;
[0067] A first sending module 404, configured to send the identity information of the user and the target position identifier to a server.
[0068] In some embodiments of the present disclosure, the system account permission management device 40 is further configured to:
[0069] Receive the account permission information corresponding to the target position identifier sent by the server;
[0070] Verify the account permission information to obtain a verification result.
[0071] In some embodiments of the present disclosure, the system account permission management device 40 is further configured to:
[0072] When the verification result is: the verification is passed, assign the account permission corresponding to the target position identifier to the user;
[0073] When the verification result is: the verification fails, generate a permission configuration failure message.
[0074] In some embodiments of the present disclosure, the system account permission management device 40 is further configured to:
[0075] Before generating a system account permission management report according to the data table to be tested and the test result table of each test batch, configure a test environment required for executing the corresponding system account permission management task according to the task description information corresponding to the system account permission management task of the test batch.
[0076] In some embodiments of the present disclosure, the system account permission management device 40 is further configured to:
[0077] Display the permission configuration failure message.
[0078] In some embodiments of the present disclosure, the determination module 402 is further configured to:
[0079] Obtain and display a position identifier information configuration table preset for the system to be applied, where the position identifier information configuration table includes: candidate position identifiers, and / or candidate position identifier groups;
[0080] Determine a target position identifier from the position identifier information configuration table according to the operation instruction.
[0081] It should be noted that the foregoing explanation of the system account permission management method also applies to the system account permission management device of this embodiment, and will not be repeated here.
[0082] In an embodiment of the present disclosure, by obtaining system account permission management tasks of multiple test batches, where each system account permission management task of a test batch has corresponding task description information, obtaining a data table to be tested corresponding to each system account permission management batch, and obtaining a test result table corresponding to each system account permission management batch, where the table structures in the data table to be tested and the test result table are the same, loading the data table to be tested and the test result table of each test batch in sequence according to the order of the multiple test batches, so as to generate a system account permission management report based on the data table to be tested and the test result table of each test batch. Thus, batch processing of system account permission management tasks can be performed, effectively improving the efficiency of system account permission management while ensuring the accuracy of system account permission management.
[0083] Figure 5 is a block diagram of a system account permission management device shown according to the present disclosure, as Figure 5 shown. The system account permission management device 50 is executed by a server. The device 50 includes:
[0084] A third receiving module 501, configured to receive the identity information of a user and a target position identifier sent by a client;
[0085] An approval module 502, configured to approve the target position identifier according to the identity information to obtain a first approval result;
[0086] A configuration module 503, configured to, when the first approval result is: approval passed, configure account permission information corresponding to the target position identifier for the user;
[0087] A second sending module 504, configured to send the account permission information corresponding to the target position identifier to the client.
[0088] It should be noted that the foregoing explanation of the system account permission management method also applies to the system account permission management device in this embodiment, and will not be elaborated here.
[0089] In an embodiment of the present disclosure, the server receives the identity information of a user and a target position identifier sent by the client, then approves the target position identifier according to the identity information to obtain a first approval result. When the first approval result is: approval passed, the server configures account permission information corresponding to the target position identifier for the user, and then sends the account permission information corresponding to the target position identifier to the client. Thus, account permission configurators can perform automatic authorization in the process, greatly improving the configuration efficiency on the basis of ensuring accurate data, reducing the workload of manual operations and the probability of errors.
[0090] Figure 6 shows a block diagram of an exemplary electronic device suitable for implementing the embodiments of the present disclosure.
[0091] Figure 6 The displayed electronic device 12 is merely an example and should not impose any limitation on the functions and scope of use of the embodiments of the present disclosure.
[0092] As Figure 6 shown, the electronic device 12 appears in the form of a general-purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 connecting different system components (including the memory 28 and the processing unit 16).
[0093] The bus 18 represents one or more of several types of bus architectures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the multiple bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnection (PCI) bus.
[0094] The electronic device 12 typically includes a variety of computer system-readable media. These media can be any available media accessible by the electronic device 12, including volatile and non-volatile media, removable and non-removable media.
[0095] The memory 28 may include computer system-readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or a cache memory 32. The electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, a storage system 34 may be used for reading and writing on non-removable, non-volatile magnetic media ( Figure 6 not shown, commonly referred to as a "hard disk drive").
[0096] Although Figure 6Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (such as a "floppy disk") can be provided, as well as an optical disk drive for reading and writing to a removable non-volatile optical disk (such as: Compact Disc Read Only Memory (hereinafter referred to as: CD-ROM), Digital Video Disc Read Only Memory (hereinafter referred to as: DVD-ROM) or other optical media). In these cases, each drive can be connected to the bus 18 through one or more data medium interfaces. The memory 28 may include at least one program product having a set (such as at least one) of program modules configured to perform the functions of the various embodiments of the present disclosure.
[0097] A program / utility 40 having a set (at least one) of program modules 42 can be stored, for example, in the memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment. The program modules 42 generally perform the functions and / or methods in the embodiments described in the present disclosure.
[0098] The electronic device 12 can also communicate with one or more external devices 14 (such as a keyboard, a pointing device, a display 24, etc.), and can also communicate with one or more devices that enable a human body to interact with the electronic device 12, and / or communicate with any device that enables the electronic device 12 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication can be carried out through the input / output (I / O) interface 22. Moreover, the electronic device 12 can also communicate with one or more networks (such as a Local Area Network (hereinafter referred to as: LAN), a Wide Area Network (hereinafter referred to as: WAN), and / or a public network, such as the Internet) through the network adapter 20. As shown in the figure, the network adapter 20 communicates with other modules of the electronic device 12 through the bus 18. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.
[0099] The processing unit 16 executes various functional applications and determines parameter information by running the programs stored in the memory 28, such as implementing the service data storage method mentioned in the foregoing embodiments, or implementing the service data acquisition method mentioned in the foregoing embodiments.
[0100] It should be noted that in the description of the present disclosure, terms such as "first", "second", etc. are only used for descriptive purposes and cannot be construed as indicating or implying relative importance. In addition, in the description of the present disclosure, unless otherwise specified, the meaning of "a plurality of" is two or more.
[0101] Any process or method description shown in a flowchart or described otherwise herein can be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a specific logical function or process. The scope of the preferred embodiments of the present disclosure includes additional implementations in which functions may be executed in a substantially simultaneous manner or in a reverse order according to the involved functions, rather than in the order shown or discussed, which should be understood by those skilled in the art to which the embodiments of the present disclosure pertain.
[0102] It should be understood that various parts of the present disclosure can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, any one or a combination of the following well-known technologies in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.
[0103] Those of ordinary skill in the art of this technology can understand that all or part of the steps carried by the method of implementing the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.
[0104] In addition, each functional unit in various embodiments of the present disclosure can be integrated into a processing module, or each unit can exist physically alone, or two or more units can be integrated into one module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.
[0105] The above-mentioned storage medium can be a read-only memory, a magnetic disk, an optical disk, etc.
[0106] In the description of this specification, the descriptions referring to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc., mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.
[0107] Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.
Claims
1. A system account authority management method, characterized in that: Executed by a client, the method comprises: Upon receiving a user's account authority application request, obtaining the user's identity information, wherein the account authority application request includes: account authority description information; Determine, according to the account authority description information, the system identification information of the system to be applied for corresponding to the user, wherein the system to be applied for has a corresponding candidate position, and each of the candidate positions has a corresponding candidate position identification; receiving an operation instruction from a user, and determining at least one target position identification from the candidate position identification information according to the operation instruction; The user's identity information and the target position identifier are sent to the server.
2. The method according to claim 1, characterized in that The method further comprises: Receiving the account authority information corresponding to the target position identifier sent by the server; The account authority information is verified to obtain a verification result.
3. The method according to claim 2, characterized in that The method further comprises: When the verification result is: verification passed, assigning the user an account authority corresponding to the target position identifier; When the verification result is: verification failed, permission configuration failure information is generated.
4. The method according to claim 3, characterized in that The method further comprises: The permission configuration failure information is displayed.
5. The method according to claim 1, characterized in that The step of determining at least one target job identifier from the candidate job identifiers according to the operation instruction includes: Obtaining and displaying a preset position identification information configuration table for the system to be applied for, wherein the position identification information configuration table includes: candidate position identifications, and / or candidate position identification groups; According to the operation instruction, the target job identification is determined from the job identification information configuration table.
6. A system account authority management method, characterized in that: Executed by the server, the method includes: Receive the user's identity information and target position identification sent by the client; Approving the target position identification according to the identity information to obtain a first approval result; When the first approval result is: approved, configuring account authority information corresponding to the target position identifier for the user; The account authority information corresponding to the target position identifier is sent to the client.
7. A system account authority management device, characterized in that: Executed by a client, the device comprises: A first receiving module is configured to obtain the identity information of the user upon receiving an account permission application request from the user, wherein the account permission application request includes: account permission description information; A determination module, configured to determine, according to the account authority description information, system identification information of the system to be applied for corresponding to the user, wherein the system to be applied for has corresponding candidate positions, and each of the candidate positions has a corresponding candidate position identification; A second receiving module, configured to receive an operation instruction from a user, and determine at least one target job identification from the candidate job identification information according to the operation instruction; The first sending module is used to send the user's identity information and the target position identifier to the server.
8. A system account authority management device, characterized in that: Executed by the server, the device includes: The third receiving module is used to receive the user's identity information and target position identification sent by the client; An approval module, used for approving the target position identification according to the identity information to obtain a first approval result; A configuration module, configured to configure account authority information corresponding to the target position identifier for the user when the first approval result is: approved; The second sending module is used to send the account authority information corresponding to the target position identifier to the client.
9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method according to any one of claims 1 to 6.
10. A computer-readable storage medium, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method according to any one of claims 1 to 6.
11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.