CN111552551A - User management method and device based on master-slave system, computer equipment and medium - Google Patents
User management method and device based on master-slave system, computer equipment and medium Download PDFInfo
- Publication number
- CN111552551A CN111552551A CN202010343932.1A CN202010343932A CN111552551A CN 111552551 A CN111552551 A CN 111552551A CN 202010343932 A CN202010343932 A CN 202010343932A CN 111552551 A CN111552551 A CN 111552551A
- Authority
- CN
- China
- Prior art keywords
- user
- slave system
- slave
- login
- request
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Computing Systems (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Hardware Design (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present application relates to the field of computers, and in particular, to a user management method, apparatus, computer device, and medium based on a master-slave system. The method comprises the following steps: receiving a user set editing request sent by a management terminal, wherein the user set editing request carries an administrator identification, and the administrator identification is used for searching a corresponding push address of a slave system; generating a corresponding editing result according to the user set editing request; and calling a pre-started first process to push the editing result to a slave system corresponding to the push address, and calling a pre-started second process to store the editing result. The method can reduce the occupation of resources. In addition, the invention also relates to a block chain technology, and the editing result can be stored in the block chain.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a user management method and apparatus based on a master-slave system, a computer device, and a medium.
Background
With the development of computer technology, internet technology and the like and the expansion of business scale of enterprise users, companies have business cooperation with other business companies such as banks, insurance and the like, and the application of data processing, data analysis and the like on the business of each company is needed.
However, conventionally, a background needs to set a plurality of systems, each system corresponds to a plurality of servers, each system also needs to configure a plurality of accounts, and different accounts log in different servers, so that the service data in each server can be processed.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a master-slave system-based user management method, apparatus, computer device, and medium capable of reducing resource occupancy.
A master-slave system based user management method, the method comprising:
receiving a user set editing request sent by a management terminal, wherein the user set editing request carries an administrator identification; the administrator identification is used for searching a corresponding push address of the slave system;
generating a corresponding editing result according to the user set editing request;
and calling a pre-started first process to push the editing result to a slave system corresponding to the push address, and calling a pre-started second process to store the editing result.
In one embodiment, the user set editing request comprises an adjustment request for role authority, an adjustment request for user information and an adjustment request for user role relationship.
In one embodiment, the editing results are stored in a blockchain.
In one embodiment, the invoking a pre-started first process to push the editing result to a slave system corresponding to the push address includes:
acquiring the type of the user set editing request, and inquiring an interface corresponding to the type;
and calling a first process to call the interface, and pushing the editing result to a slave system corresponding to the pushing address.
In one embodiment, the method further comprises:
receiving a main system login request sent by a user terminal, wherein the main system login request carries a user identifier;
logging in a main system according to the user identification, and returning a main system login interface to the user terminal, wherein the main system login interface displays an icon link of a slave system accessed to the main system;
receiving a slave system login request through an icon link of a slave system on the master system login interface, wherein the slave system login request carries the user identifier;
and logging in the corresponding slave system through the user identification.
In one embodiment, the logging in the corresponding slave system through the user identifier includes:
generating a corresponding service label and the current operation identifier according to the user identifier;
the service label and the current operation identification are sent to a slave system, so that after the slave system verifies the service label, a password verification interface of the master system is called to verify the service label and the current operation identification, after the service label and the current operation identification are verified, user information corresponding to the service label is verified, and after the user information is verified successfully, information of successful verification is fed back to the master system;
and when the information of successful verification sent by the slave system is received, jumping to a menu interface of the slave system, and feeding the menu interface back to the user terminal.
In one embodiment, after the generating a corresponding service tag and an identifier of the operation of this time according to the user identifier and sending the service tag and the identifier of the operation of this time to the slave system, the method further includes:
acquiring the authority corresponding to the user identification, and sending the authority to a slave system, so that the slave system acquires corresponding menu content according to the authority after successfully verifying the user information, and generates a corresponding menu interface;
the jump to the menu interface of the slave system comprises:
and jumping to the menu interface generated by the slave system.
In one embodiment, the method further comprises:
receiving a login state query request sent by a system;
inquiring the login state of the main system according to the login state inquiry request;
and feeding back the inquired login state to the slave system, so that the slave system adjusts the login state of the slave system according to the login state of the master system.
A master-slave system based user management apparatus, the apparatus comprising:
the first receiving module is used for receiving a user set editing request sent by a management terminal, wherein the user set editing request carries an administrator identifier; the administrator identification is used for searching a corresponding push address of the slave system;
the editing result generating module is used for generating a corresponding editing result according to the user set editing request;
and the pushing module is used for calling a pre-started first process to push the editing result to the slave system corresponding to the pushing address, and calling a pre-started second process to store the editing result.
A computer device comprising a memory storing a computer program and a processor implementing the steps of any of the methods described above when the processor executes the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any of the above.
According to the user management method, the user management device, the computer equipment and the user management medium based on the master-slave system, the user set editing request is received in the master system, the editing result is correspondingly generated, and the result is pushed to the corresponding slave system, so that the users of the master-slave system are completely consistent, a large number of accounts do not need to be set for the master-slave system, the slave system can be logged in through one account only needing to be set in the master system, and the resource occupation is reduced.
Drawings
FIG. 1 is a diagram illustrating an exemplary embodiment of a user management method based on a master-slave system;
FIG. 2 is a flow chart illustrating a user management method based on a master-slave system in one embodiment;
FIG. 3 is a flow diagram of a method for logging in from a system, under an embodiment;
FIG. 4 is a block diagram of a user management device based on a master-slave system in one embodiment;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The user management method based on the master-slave system can be applied to the application environment shown in fig. 1. Wherein the management terminal 102 communicates with the host system 104 via a network. The master system 104 communicates with the slave system 106 over a network. The master system 104 may receive a user set editing request sent by the management terminal 102, where the user set editing request carries an administrator identifier, and the administrator identifier is used to search for a push address of a corresponding slave system; thus, the main system 102 can generate a corresponding editing result according to the user set editing request; therefore, the main system 104 calls the pre-started first process to push the editing result to the slave system 106 corresponding to the pushing address, and calls the pre-started second process to store the editing result, so that a large number of accounts do not need to be set for the main system and only one account needs to be set in the main system to log in the slave system through the account, and the occupation of resources is reduced. The management terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the master system 104 and the slave system 106 may be implemented by independent servers or a server cluster composed of a plurality of servers.
In one embodiment, as shown in fig. 2, a user management method based on a master-slave system is provided, which is described by taking the method as an example applied to the master system in fig. 1, and includes the following steps:
s202: and receiving a user set editing request sent by the management terminal, wherein the user set editing request carries an administrator identification, and the administrator identification is used for searching a corresponding push address of the slave system.
Specifically, the user set editing request is a request received by a front end corresponding to the host system to modify, add, or delete a user, a role, or user information. Different front ends correspond to different administrators, and different administrators can manage different users, for example, users who can log in to the slave systems managed by the front ends, user information of the users, corresponding roles, and the like. Assuming that there are administrator a and administrator B, administrator a corresponds to slave systems C1, C2, C3, and administrator B corresponds to slave systems D1, D2, D3, where administrator a may manage users F1, F2, F3, F4, and administrator B may manage users F3, F4, F5, F6, so that users F1, F2, F3, F4 may log in slave systems C1, C2, C3, and users F3, F4, F5, F6 may log in slave systems D1, D2, D3.
S204: and generating a corresponding editing result according to the user set editing request.
Specifically, the editing result is generated according to the user set editing request, and includes adding a new role, assigning a menu to a role, modifying role information, adding a new user, user information, deleting a user, and the like.
S206: and calling a pre-started first process to push the editing result to a slave system corresponding to the push address, and calling a pre-started second process to store the editing result.
Specifically, the first process and the second process may be started in advance, for example, after the host system generates a corresponding editing result according to the user set editing request, the first process and the second process may be started, and the first process and the second process enter a waiting state, so that after the host system queries the push address, the host system may call the first process started in advance to push the editing result to the slave system corresponding to the push address, and call the second process started in advance to store the editing result. And optionally, the second process may also be a main process in the main system, that is, the process of performing the above steps S202 to S204.
In order to ensure the privacy and security of the editing result, the editing result can also be stored in a node of a block chain. The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.
Since the consistency of users of the master-slave system is to be achieved, after the editing result is obtained, the editing result is saved in the master system on one hand, and is pushed to the slave system on the other hand, in order to improve efficiency, the operation may be performed through multiple processes, and optionally, when the master system calls the first process to push the editing result to the slave system corresponding to the push address, the pushing may be performed when a scene needing pushing is triggered, for example, when a timing task is due. Because a plurality of slave systems need to be pushed, a single-process multi-thread mode can be adopted, for example, threads corresponding to the number of the slave systems are started, and then pushing is performed in parallel, so that the pushing efficiency can be further improved.
Specifically, the master system invokes the pre-started first process to query a slave system corresponding to the administrator identifier, and obtains a push address corresponding to the queried slave system, and then pushes the editing result to the slave system corresponding to the push address. Or the master system inquires the slave system corresponding to the administrator identification in advance, acquires the push address corresponding to the inquired slave system, and then calls the first process started in advance to push the editing result to the slave system corresponding to the push address. Specifically, the master system may query all slave systems under the administrator according to the administrator identification in the first process or in advance, store those slave systems in the memory that need to be pushed, and record the pushing address so as to facilitate subsequent pushing.
In addition, the slave system can also manage the editing result pushed by the master system, such as changing the authority and the like, so that the personalized management of the slave system can be realized. Namely, the personalized management is realized on the premise of not interfering the user of the main system and the users of other slave systems.
According to the user management method based on the master-slave system, the user set editing request is received in the master system, the editing result is correspondingly generated, and the result is pushed to the corresponding slave system, so that users of the master-slave system are completely consistent, a large number of accounts do not need to be set for the master-slave system, the slave system can be logged in through one account only needing to be set in the master system, and the resource occupation is reduced.
In one embodiment, the user set editing request comprises an adjustment request for role authority, an adjustment request for user information and an adjustment request for user role relationship.
In one embodiment, calling a pre-started first process to push an editing result to a slave system corresponding to a push address includes: acquiring the type of a user set editing request, and inquiring an interface corresponding to the type; and calling the first process to call the interface, and pushing the editing result to the slave system corresponding to the pushing address.
Specifically, the above-mentioned generating a corresponding editing result according to the user set editing request may include 3 scenarios: the role relationship adjustment method comprises the steps of adjusting requests for role authorities, adjusting requests for user information and adjusting requests for user role relationships. The host system thus provides 3 interface protocols: a: role authority interface, B: user information interface, C: the user role relationship interface and the accessed slave system need to realize three interfaces according to a protocol.
Specifically, when a role is newly added, a menu is given to the role, and role information is modified, an interface A is called to push data; when a user is newly added, the interfaces B and C are called to push data; and calling the interface B to push data when the user information is modified or the user is deleted, and calling the interface C to push when the user is endowed with a role.
In the above embodiment, different interfaces are set for different operation requests, so that the accuracy of pushing is ensured.
In one embodiment, please refer to fig. 3, where fig. 3 is a flowchart of a slave system login method in an embodiment, the user management method based on a master-slave system further includes the slave system login method applied to a master system, and specifically includes the following steps:
s302: and receiving a main system login request sent by the user terminal, wherein the main system login request carries the user identifier.
Specifically, the main system login request may be sent by the user terminal, that is, the user terminal inputs a web address of the main system in the browser, then opens an interface of the main system, and the user inputs an account and a password, that is, a user identifier, so that the user terminal sends the account and the password to the main system, and the main system verifies the account and the password, and if the verification is successful, the main system login is successful.
S304: and logging in the main system according to the user identification, and returning a main system login interface to the user terminal, wherein the main system login interface displays an icon link of a slave system accessed to the main system.
Specifically, the main system login interface is an interface displayed with a slave system accessing the main system, specifically, the main system can determine an account, namely the slave system which the user can log in, and then display login interface identifiers of the slave systems on the main system login interface, so that the user can conveniently select the slave system to be logged in. And the main system sends the main system login interface to the user terminal for displaying.
S306: and receiving a slave system login request through an icon link of a slave system on the main system login interface, wherein the slave system login request carries the user identification.
Specifically, the user terminal may receive a selection of a user to determine a slave system that the user logs in this time, and generate a slave system login request according to the user currently logging in the master system, so as to determine the user who logs in the slave system, and optionally, after the user clicks one of the slave system login interfaces each time, the browser restarts a page to perform a jump, that is, a jump to a new page, to log in the slave system, that is, a jump to the slave system login page.
S308: and logging in the corresponding slave system through the user identification.
Specifically, after receiving a slave system login request returned by the user terminal, the master system forwards the slave system login request to the corresponding slave system, so that the slave system logs in the slave system after processing, that is, the slave system returns login success information to the master system after processing, so that the master system returns the login success information to the user terminal, and thus, a browser of the user terminal can jump to a menu interface of the slave system.
In the embodiment, a plurality of web login interfaces are not required to be set, only the main system login interface is required to be set, and the login interfaces of all the slave systems which can be logged in by the current user are navigated through the login interfaces, so that the user can log in the slave systems only by clicking the slave systems which need to be logged in, the method is simple and convenient, and the occupation of computer resources is reduced.
In one embodiment, logging in a corresponding slave system through user identification comprises: generating a corresponding service label and the current operation identifier according to the user identifier; the service tag and the operation identification are sent to the slave system, so that the slave system is used for verifying the service tag, then a password verification interface of the master system is called to verify the service tag and the operation identification, after the service tag and the operation identification are verified, user information corresponding to the service tag is verified, and after the user information is verified successfully, information of successful verification is fed back to the master system; and when the information of successful verification sent by the slave system is received, jumping to a menu interface of the slave system, and feeding the menu interface back to the user terminal.
Specifically, in order to implement single sign-on, in this embodiment, the master system implements authentication and unified management on the user, and may perform rights management and role management on the user, and when accessing the slave system, the slave system menu rights may be displayed according to the user rights.
Thus, the host system generates a corresponding service tag and the operation identifier at this time according to the user identifier, that is, the host system generates a ssoTicket (encrypted user ID, timestamp, signature, etc.) for single sign-on. When a master system accesses a slave system, a user transmits ssoTicket and bankId as parameters, the slave system verifies the ssoTicket after receiving a request, the verification process is to call a password verification interface of the master system to take ssotickey and bankID as access parameters, the password verification interface returns a verification result, if the password verification is not passed, login failure is returned from the system, the slave system verifies user information after the password verification is passed, if the user information is matched with the slave system user information, the slave system is jumped successfully, the user can access a slave system page, otherwise, the user is prompted to have no or other corresponding information and returns to the master system login page.
The slave system can delete the user information, which can cause the verification failure, i.e. the user of the master system can be managed in a personalized way on the premise of not influencing the user of the master system.
In addition, after receiving a slave system login request returned by the user terminal, the master system forwards the slave system login request to the corresponding slave system, so that the slave system logs in the slave system after processing, namely, the slave system returns login success information to the master system after processing, and the master system returns the login success information to the user terminal, so that a browser of the user terminal can jump to a menu interface of the slave system.
In the above embodiment, the access of the slave system is realized through single sign-on, and independent access of a plurality of slave systems can be realized on the premise of not influencing the main system.
In one embodiment, after generating a corresponding service tag and an identifier of the operation according to the user identifier and sending the service tag and the identifier of the operation to the slave system, the method further includes: acquiring the authority corresponding to the user identification, and sending the authority to the slave system, so that the slave system acquires the corresponding menu content according to the authority after successfully verifying the user information, and generates a corresponding menu interface; jumping to a menu interface of the slave system, comprising: a jump is made to a menu interface generated from the system.
Specifically, the master system acquires the authority corresponding to the user identifier and sends the authority to the slave system, so that the slave system acquires the menu content corresponding to the slave system according to the authority after the user information is successfully verified, and generates a corresponding menu interface, and therefore when the information which is successfully verified and sent by the slave system is received, the slave system jumps to the menu interface of the slave system and feeds the menu interface back to the user terminal.
The process of logging in the slave system through the master system will be described in detail with reference to the above login process, which mainly includes:
the user sends a login request to a main system on a front-end web page, the main system generates single-point login ssoTicket (encrypted user ID, timestamp, signature and the like) after judging that the user is a legal user (single-point login: the same user generates a unique bill during each login), the single-point login ssoTicket is generated according to the ID of the user, the signature is added according to the user ID and the timestamp, and meanwhile bankid to which the login user belongs is also obtained. When a user clicks a certain subsystem at the main system, the main system calls a login interface of the subsystem and sends ssoTicket and bankid to the subsystem. The subsystem calls a password verification interface of the main system after receiving the request, and the main system verifies whether ssoTicket and bankid are legal or not and informs the result to the subsystem. If the verification result is passed, the subsystem judges whether the user exists in the subsystem, which authorities exist and the like, if the user exists, the page and the page menu of the subsystem are displayed according to the authority of the user, and if the user does not exist, the user is prompted to not exist and the jump to the main system is interrupted. And if the password verification fails, prompting error information and interrupting the jump to return to the login page of the main system.
In the embodiment, different menu interfaces are displayed according to the user permission, so that the user can only operate corresponding content, and data security is ensured.
In one embodiment, the user management method based on the master-slave system further includes: receiving a login state query request sent by a system; inquiring the login state of the main system according to the login state inquiry request; and feeding back the inquired login state to the slave system, so that the slave system adjusts the login state of the slave system according to the login state of the master system.
The embodiment mainly introduces a session maintaining step, in which the session timeout time of the slave system and the session timeout time of the associated system are kept consistent, and if the session of the master system is timed out, the slave system logs in for timeout; and the slave system calls a refresh login state interface of the master system to realize session maintenance, otherwise, the session is interrupted, and the user logs out. If the time-out occurs when the host system is invoked to refresh the login state interface, the user logs out and can no longer access the slave system.
Specifically, the determining, by the master system, whether the slave system performs session maintenance specifically may include:
the host system judges timeout according to user operation after the user logs in, for example, the timeout is judged if no operation is performed within 5 minutes by the user. After the user jumps from the master system to the slave system, it will time out within 5 minutes if there is no operation at the master system. The refresh entry state interface of the host system, which will re-register a timeout after a call, needs to be called every 5 minutes from the system to refresh the timeout. Similarly, if the user has not been operating at the subsystem for more than a fixed time, the subsystem will not invoke the refresh login state interface and the user will log out over time. If the subsystem has timed out when it calls to refresh the login state interface, the user will also log out.
In the above embodiment, normal access from the system is guaranteed by session maintenance.
It should be understood that although the various steps in the flow charts of fig. 2-3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 4, there is provided a master-slave system-based user management apparatus, including: the first receiving module 100, the editing result generating module 200, the push address querying module 300, and the push module 400, wherein:
a first receiving module 100, configured to receive a user set editing request sent by a management terminal, where the user set editing request carries an administrator identifier, and the administrator identifier is used to search a corresponding push address of a slave system;
an edit result generation module 200, configured to generate a corresponding edit result according to the user set edit request;
the pushing module 300 is configured to invoke a pre-started first process to push the editing result to the slave system corresponding to the push address, and invoke a pre-started second process to store the editing result.
In one embodiment, the user set editing request comprises an adjustment request for role authority, an adjustment request for user information and an adjustment request for user role relationship.
In one embodiment, the editing results are stored in a blockchain.
In one embodiment, the pushing module 300 may include:
the interface acquisition unit is used for acquiring the type of the user set editing request and inquiring an interface corresponding to the type;
and the pushing unit is used for calling the first process to call the interface and pushing the editing result to the slave system corresponding to the pushing address.
In one embodiment, the master-slave system-based user management apparatus may further include:
the second receiving module is used for receiving a main system login request sent by the user terminal, wherein the main system login request carries the user identifier;
the system comprises a main system login module, a user terminal and a main system display module, wherein the main system login module is used for logging in a main system according to a user identifier and returning a main system login interface to the user terminal, and the main system login interface displays an icon link of a slave system accessed to the main system;
the third receiving module is used for receiving a slave system login request through an icon link of a slave system on a master system login interface, wherein the slave system login request carries a user identifier;
and the slave system login module is used for logging in the corresponding slave system through the user identification.
In one embodiment, the slave system login module may include:
the identification generation unit is used for generating a corresponding service label and the current operation identification according to the user identification;
the first verification unit is used for sending the service label and the current operation identifier to the slave system, so that the slave system can verify the service label and then call a password verification interface of the master system to verify the service label and the current operation identifier, verify the user information corresponding to the service label after the service label and the current operation identifier are verified, and feed back the information of successful verification to the master system after the user information is verified successfully;
and the login unit is used for jumping to a menu interface of the slave system and feeding back the menu interface to the user terminal after receiving the information of successful verification sent by the slave system.
In one embodiment, the slave system login module may further include:
the second verification unit is used for acquiring the authority corresponding to the user identifier and sending the authority to the slave system, so that the slave system acquires the corresponding menu content according to the authority after successfully verifying the user information and generates a corresponding menu interface;
the login unit is also used for jumping to a menu interface generated from the system.
In one embodiment, the master-slave system-based user management apparatus may further include:
the fourth receiving module is used for receiving the login state inquiry request sent by the system;
the login state query module is used for querying the login state of the main system according to the login state query request;
and the session maintaining module is used for feeding back the inquired login state to the slave system so that the slave system adjusts the login state of the slave system according to the login state of the master system.
For specific limitations of the user management device based on the master-slave system, reference may be made to the above limitations of the user management method based on the master-slave system, which are not described herein again. The modules in the user management device based on the master-slave system can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing editing results and data of users, roles and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a master-slave system based user management method.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a computer device comprising a memory storing a computer program and a processor implementing the following steps when the processor executes the computer program: receiving a user set editing request sent by a management terminal, wherein the user set editing request carries an administrator identification which is used for searching a corresponding push address of a slave system; generating a corresponding editing result according to the user set editing request; and calling a pre-started first process to push the editing result to a slave system corresponding to the push address, and calling a pre-started second process to store the editing result.
In one embodiment, the user set editing requests involved in the execution of the computer program by the processor include adjustment requests for role privileges, adjustment requests for user information, and adjustment requests for user role relationships.
In one embodiment, the editing results are stored in a blockchain.
In one embodiment, invoking a pre-launched first process implemented when the processor executes the computer program pushes the editing result to a slave system corresponding to the push address, comprising: acquiring the type of a user set editing request, and inquiring an interface corresponding to the type; and calling the first process to call the interface, and pushing the editing result to the slave system corresponding to the pushing address.
In one embodiment, the processor, when executing the computer program, further performs the steps of: receiving a main system login request sent by a user terminal, wherein the main system login request carries a user identifier; logging in a main system according to the user identification, and returning a main system login interface to the user terminal, wherein the main system login interface displays an icon link of a slave system accessed to the main system; receiving a slave system login request through an icon link of a slave system on a master system login interface, wherein the slave system login request carries a user identifier; and logging in the corresponding slave system through the user identification.
In one embodiment, the logging in of a corresponding slave system by a user identification, as implemented by a processor executing a computer program, comprises: generating a corresponding service label and the current operation identifier according to the user identifier; the service tag and the operation identification are sent to the slave system, so that the slave system is used for verifying the service tag, then a password verification interface of the master system is called to verify the service tag and the operation identification, after the service tag and the operation identification are verified, user information corresponding to the service tag is verified, and after the user information is verified successfully, information of successful verification is fed back to the master system; and when the information of successful verification sent by the slave system is received, jumping to a menu interface of the slave system, and feeding the menu interface back to the user terminal.
In one embodiment, the implementation of the processor when executing the computer program, after generating the corresponding service tag and the identifier of the current operation according to the user identifier and sending the service tag and the identifier of the current operation to the slave system, further includes: acquiring the authority corresponding to the user identification, and sending the authority to the slave system, so that the slave system acquires the corresponding menu content according to the authority after successfully verifying the user information, and generates a corresponding menu interface; a jump to a menu interface of a slave system implemented by a processor executing a computer program, comprising: a jump is made to a menu interface generated from the system.
In one embodiment, the processor, when executing the computer program, further performs the steps of: receiving a login state query request sent by a system; inquiring the login state of the main system according to the login state inquiry request; and feeding back the inquired login state to the slave system, so that the slave system adjusts the login state of the slave system according to the login state of the master system.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving a user set editing request sent by a management terminal, wherein the user set editing request carries an administrator identification which is used for searching a corresponding push address of a slave system; generating a corresponding editing result according to the user set editing request; and calling a pre-started first process to push the editing result to a slave system corresponding to the push address, and calling a pre-started second process to store the editing result.
In one embodiment, the user set editing requests to which the computer program refers when executed by the processor include adjustment requests for role privileges, adjustment requests for user information, and adjustment requests for user role relationships.
In one embodiment, invoking a pre-launched first process, implemented when the computer program is executed by the processor, to push the editing result to the slave system corresponding to the push address includes: acquiring the type of a user set editing request, and inquiring an interface corresponding to the type; and calling the first process to call the interface, and pushing the editing result to the slave system corresponding to the pushing address.
In one embodiment, the computer program when executed by the processor further performs the steps of: receiving a main system login request sent by a user terminal, wherein the main system login request carries a user identifier; logging in a main system according to the user identification, and returning a main system login interface to the user terminal, wherein the main system login interface displays an icon link of a slave system accessed to the main system; receiving a slave system login request through an icon link of a slave system on a master system login interface, wherein the slave system login request carries a user identifier; and logging in the corresponding slave system through the user identification.
In one embodiment, a computer program, when executed by a processor, implements logging in a corresponding slave system via user identification, comprising: generating a corresponding service label and the current operation identifier according to the user identifier; the service tag and the operation identification are sent to the slave system, so that the slave system is used for verifying the service tag, then a password verification interface of the master system is called to verify the service tag and the operation identification, after the service tag and the operation identification are verified, user information corresponding to the service tag is verified, and after the user information is verified successfully, information of successful verification is fed back to the master system; and when the information of successful verification sent by the slave system is received, jumping to a menu interface of the slave system, and feeding the menu interface back to the user terminal.
In one embodiment, the implementation of the computer program when executed by the processor, after generating a corresponding service tag and an identifier of the current operation according to a user identifier and sending the service tag and the identifier of the current operation to the slave system, further includes: acquiring the authority corresponding to the user identification, and sending the authority to the slave system, so that the slave system acquires the corresponding menu content according to the authority after successfully verifying the user information, and generates a corresponding menu interface; a jump to a menu interface of a slave system implemented by a computer program when executed by a processor, comprising: a jump is made to a menu interface generated from the system.
In one embodiment, the computer program when executed by the processor further performs the steps of: receiving a login state query request sent by a system; inquiring the login state of the main system according to the login state inquiry request; and feeding back the inquired login state to the slave system, so that the slave system adjusts the login state of the slave system according to the login state of the master system.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A master-slave system based user management method, the method comprising:
receiving a user set editing request sent by a management terminal, wherein the user set editing request carries an administrator identification; the administrator identification is used for searching a corresponding push address of the slave system;
generating a corresponding editing result according to the user set editing request;
and calling a pre-started first process to push the editing result to a slave system corresponding to the push address, and calling a pre-started second process to store the editing result.
2. The method of claim 1, wherein the user set editing request comprises an adjustment request for role authority, an adjustment request for user information, and an adjustment request for user role relationship.
3. The method of claim 1, wherein the invoking the first process to push the editing result to the slave system corresponding to the push address comprises:
acquiring the type of the user set editing request, and inquiring an interface corresponding to the type;
and calling a first process to call the interface, and pushing the editing result to a slave system corresponding to the pushing address.
4. A method according to any one of claims 1 to 3, characterized in that the method further comprises:
receiving a main system login request sent by a user terminal, wherein the main system login request carries a user identifier;
logging in a main system according to the user identification, and returning a main system login interface to the user terminal, wherein the main system login interface displays an icon link of a slave system accessed to the main system;
receiving a slave system login request through an icon link of a slave system on the master system login interface, wherein the slave system login request carries the user identifier;
and logging in the corresponding slave system through the user identification.
5. The method of claim 4, wherein the logging in the corresponding slave system through the user identifier comprises:
generating a corresponding service label and the current operation identifier according to the user identifier;
the service label and the current operation identification are sent to a slave system, so that after the slave system verifies the service label, a password verification interface of the master system is called to verify the service label and the current operation identification, after the service label and the current operation identification are verified, user information corresponding to the service label is verified, and after the user information is verified successfully, information of successful verification is fed back to the master system;
and when the information of successful verification sent by the slave system is received, jumping to a menu interface of the slave system, and feeding the menu interface back to the user terminal.
6. The method according to claim 5, wherein after generating the corresponding service tag and the current operation identifier according to the user identifier and sending the service tag and the current operation identifier to the slave system, the method further comprises:
acquiring the authority corresponding to the user identification, and sending the authority to a slave system, so that the slave system acquires corresponding menu content according to the authority after successfully verifying the user information, and generates a corresponding menu interface;
the jump to the menu interface of the slave system comprises:
and jumping to the menu interface generated by the slave system.
7. The method of claim 4, further comprising:
receiving a login state query request sent by a system;
inquiring the login state of the main system according to the login state inquiry request;
and feeding back the inquired login state to the slave system, so that the slave system adjusts the login state of the slave system according to the login state of the master system.
8. A master-slave system based user management apparatus, the apparatus comprising:
the first receiving module is used for receiving a user set editing request sent by a management terminal, wherein the user set editing request carries an administrator identifier; the administrator identification is used for searching a corresponding push address of the slave system;
the editing result generating module is used for generating a corresponding editing result according to the user set editing request;
and the pushing module is used for calling a pre-started first process to push the editing result to the slave system corresponding to the pushing address, and calling a pre-started second process to store the editing result.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010343932.1A CN111552551A (en) | 2020-04-27 | 2020-04-27 | User management method and device based on master-slave system, computer equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010343932.1A CN111552551A (en) | 2020-04-27 | 2020-04-27 | User management method and device based on master-slave system, computer equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111552551A true CN111552551A (en) | 2020-08-18 |
Family
ID=72004039
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010343932.1A Pending CN111552551A (en) | 2020-04-27 | 2020-04-27 | User management method and device based on master-slave system, computer equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111552551A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407740A (en) * | 2021-05-11 | 2021-09-17 | 北京达佳互联信息技术有限公司 | Multimedia collection management method and device and electronic equipment |
-
2020
- 2020-04-27 CN CN202010343932.1A patent/CN111552551A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407740A (en) * | 2021-05-11 | 2021-09-17 | 北京达佳互联信息技术有限公司 | Multimedia collection management method and device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110781482B (en) | Login method, login device, computer equipment and storage medium | |
| CN108833521B (en) | Message pushing method, device, system, computer equipment and storage medium | |
| CN111666514A (en) | Data processing method and device for realizing cross-domain request at webpage end and related equipment | |
| CN110602169B (en) | Service calling method and device, computer equipment and storage medium | |
| CN111625301A (en) | Idempotent processing method, apparatus, device and storage medium | |
| CN110764700A (en) | Data storage method and device, computer equipment and storage medium | |
| CN109144487B (en) | Method, device, computer equipment and storage medium for developing business of parts | |
| CN110213392B (en) | Data distribution method and device, computer equipment and storage medium | |
| CN108418797B (en) | Webpage access method and device, computer equipment and storage medium | |
| CN112860778B (en) | Database management method, device, equipment and medium for desktop application program | |
| CN111475795A (en) | Method and device for unified authentication and authorization facing to multiple applications | |
| CN112468540B (en) | Cloud platform-based data distribution method, equipment and medium | |
| CN112527835B (en) | Authentication request processing method and device based on cache and related equipment | |
| CN112651001A (en) | Access request authentication method, device, equipment and readable storage medium | |
| CN114119300A (en) | Electronic protocol matching method and device, computer equipment and storage medium | |
| CN112016122A (en) | Webpage data processing method and device, computer equipment and storage medium | |
| CN110598452B (en) | Evidence information processing method, device, storage medium and equipment based on blockchain | |
| CN111026988A (en) | Page loading method, device and system and computer equipment | |
| CN110597820A (en) | Block chain based information processing method and device, storage medium and equipment | |
| CN111552551A (en) | User management method and device based on master-slave system, computer equipment and medium | |
| CN111327680B (en) | Authentication data synchronization method, device, system, computer equipment and storage medium | |
| CN109525613B (en) | Request processing system and method | |
| CN111901383A (en) | Data request processing method and device, computer equipment and storage medium | |
| CN116010926A (en) | Login authentication method, login authentication device, computer equipment and storage medium | |
| CN112583890B (en) | Message pushing method and device based on enterprise office system and computer equipment |
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 |