CN117978855A - User operation termination method, device, server and storage medium - Google Patents

Abstract

The present invention provides a user operation termination method, device, server and storage medium, the method comprising: monitoring the service call triggered by the user operation in the distributed system, creating a call chain context object for the service call; saving the user identity information in the call chain context object; obtaining the user identity information, intercepting the service call being executed triggered by the user identity information, and generating the interception identity information range; before the service is formally called, obtaining the call chain context object, extracting the user identity information from the call chain context object, and judging whether the user identity information is within the interception identity information range; if it is judged that the user identity information is not within the interception identity information range, continuing the service call; if it is judged that the user identity information is within the interception identity information range, terminating the service call. The instant termination of the service call in the background flow of the distributed system is realized.

Description

User operation termination method, device, server and storage medium

Technical Field

The present invention relates to the field of computer technology, and in particular to a user operation termination method, device, server and storage medium.

Background technique

A distributed system is a system whose components are distributed across connected computers and communicate and coordinate actions through message passing. The definition of a distributed system introduces the following important characteristics of a distributed system: concurrency of components, lack of a global clock, and independence of component failures.

The user operation termination method applicable to the distributed system in the prior art is usually based on the Web session management framework to delete or disable the Web session instance of the specified user in the distributed system background, so that the user's next operation will be terminated due to session verification failure.

However, the user operation termination method applicable to the distributed system in the prior art has the following disadvantages: it can only terminate the next operation of the user, and cannot immediately terminate the service call that is still circulating in the background of the distributed system.

Summary of the invention

The present invention provides a user operation termination method, device, server and storage medium to solve the problem in the prior art that the user operation termination method applicable to a distributed system can only terminate the user's next operation but cannot immediately terminate the service call that is still circulating in the background of the distributed system.

In a first aspect, the present invention provides a user operation termination method, comprising:

Monitor the service calls triggered by user operations in the distributed system, and create a call chain context object for the service calls;

The user identity information is stored in the call chain context object, so that the user identity information is kept transmitted on the distributed call chain;

Obtaining user identity information, intercepting the executing service call triggered by the user identity information, and generating an interception identity information range;

Before the service is formally called, the call chain context object is obtained, the user identity information is extracted from the call chain context object, and it is determined whether the user identity information is within the scope of the intercepted identity information;

If it is determined that the user identity information is not within the intercepted identity information range, continue the service call;

If it is determined that the user identity information is within the interception identity information range, the service call is terminated, and an abnormal signal and interception details are generated;

The abnormal signal and the interception details are received, wherein the interception details include user identity information, interception time, and terminated service call.

In a possible design, before monitoring the service call triggered by the user operation, it also includes: receiving the user's login identity authentication information, generating an encrypted string based on the login identity authentication information; verifying the user's identity based on the string, if the verification passes, executing the user operation to trigger the service call; if the verification fails, sending a notification of verification failure to the user end.

In a possible design, after monitoring the service call triggered by the user operation, it also includes: obtaining the user's request header field; and decrypting the request header field to obtain the user identity information.

In one possible design, the method of obtaining user identity information, intercepting the ongoing service call triggered by the user identity information, and generating an interception identity information range includes: obtaining user identity information; sending an interception instruction, and broadcasting the interception instruction; intercepting the ongoing service call triggered by the user identity information according to the interception instruction, and generating an interception identity information range.

In one possible design, the method of obtaining user identity information, intercepting the ongoing service call triggered by the user identity information, and generating the interception identity information range further includes: after the service is called, obtaining the call chain context object, extracting the user identity information from the call chain context object, and determining whether the user identity information is within the interception identity information range; if it is determined that the user identity information is not within the interception identity information range, returning the service processing result; if it is determined that the user identity information is within the interception identity information range, terminating the return of the service processing result and generating an abnormal signal and an interception detail; receiving the abnormal signal and the interception detail, wherein the interception detail includes the user identity information, the interception time, and the terminated service call.

In one possible design, the service call includes one or more of the following: calling an ajax interface, executing a local java method, executing an asynchronous thread, sending an asynchronous message, scheduling a timed task, calling a remote service, and accessing a database.

In a second aspect, the present invention provides a user operation termination device, comprising: a monitoring module, which is used to monitor service calls triggered by user operations in a distributed system and create a call chain context object for the service call; a saving module, which is used to save user identity information in the call chain context object so that the user identity information can be kept transmitted on the distributed call chain; an interception module, which is used to obtain user identity information, intercept the service call in execution triggered by the user identity information, and generate an interception identity information range; an extraction module, which is used to obtain the call chain context object before the service is formally called, extract the user identity information from the call chain context object, and determine whether the user identity information is within the interception identity information range; a service calling module, which is used to continue the service call if it is determined that the user identity information is not within the interception identity information range; a termination module, which is used to terminate the service call if it is determined that the user identity information is within the interception identity information range, and generate an abnormal signal and an interception detail; a receiving module, which is used to receive the abnormal signal and the interception detail, wherein the interception detail includes the user identity information, the interception time, and the terminated service call.

In a possible design, the user operation termination device also includes: a verification module, which is used to receive the user's login identity authentication information, and generate an encrypted string based on the login identity authentication information; verify the user's identity based on the string, and if the verification passes, execute the user operation to trigger the service call; if the verification fails, send a notification of verification failure to the user end.

In a third aspect, the present invention provides a server, comprising: at least one processor and a memory;

The memory stores computer-executable instructions;

The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the user operation termination method described in the first aspect and various possible designs of the first aspect.

In a fourth aspect, the present invention provides a computer storage medium, wherein the computer storage medium stores computer execution instructions. When a processor executes the computer execution instructions, the user operation termination method described in the first aspect and various possible designs of the first aspect is implemented.

The user operation termination method, device, server and storage medium provided by the present invention monitor the service call triggered by the user operation in the distributed system, create a call chain context object for the service call; save the user identity information in the call chain context object so that the user identity information can be kept transmitted on the distributed call chain; obtain the user identity information, intercept the service call in progress triggered by the user identity information, and generate an interception identity information range; before the service is formally called, obtain the call chain context object, extract the user identity information from the call chain context object, if it is determined that the user identity information is not within the interception identity information range, continue the service call; if it is determined that the user identity information is within the interception identity information range, terminate the service call, and generate an abnormal signal and interception details; receive the abnormal signal and interception details, wherein the interception details include the user identity information, the interception time and the terminated service call, so as to realize the instant termination of the service call in the background flow of the distributed system.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

FIG1 is a schematic diagram of a first flow chart of a method for terminating a user operation provided by an embodiment of the present invention;

FIG2 is a second flow chart of a method for terminating a user operation provided by an embodiment of the present invention;

FIG3 is a schematic diagram of a third flow chart of a method for terminating a user operation provided by an embodiment of the present invention;

FIG4 is a schematic diagram of the structure of a user operation termination device provided by an embodiment of the present invention;

FIG. 5 is a schematic diagram of the hardware structure of a server provided in an embodiment of the present invention.

Detailed ways

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

It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and corresponding operation entrances shall be provided for users to choose to authorize or refuse.

A distributed system is a system whose components are distributed on connected computers, and the components communicate and coordinate actions through message passing. The definition of a distributed system introduces the following important features of a distributed system: concurrency of components, lack of global clocks, and independence of component failures. The user operation termination method applicable to a distributed system in the prior art is usually based on a Web session management framework, which deletes or disables the Web session instance of a specified user in the background of the distributed system, so that the user's next operation will be terminated due to session verification failure. However, the user operation termination method applicable to a distributed system in the prior art has the following disadvantages: it can only terminate the user's next operation, and cannot immediately terminate the service call that is still circulating in the background of the distributed system. In addition, the existing method is code-invasive, and the implementation scheme based on the session management framework requires the selection of the session management framework and targeted transformation of the code extension function. In addition, there is also the problem of a single processing level, because it is implemented by disabling the Web session, which is only applicable to web page operations, and is not applicable to scenarios such as asynchronous messages and remote service calls.

In order to solve the above technical problems, an embodiment of the present invention proposes the following inventive concept: by monitoring the service calls triggered by user operations in a distributed system, the user identity information is saved in the call chain context object, the user identity information is obtained and it is determined whether the user identity information is within the intercepted identity information range. If so, the service call is terminated to realize the termination of user operations in the distributed system.

FIG1 is a flow chart of a method for terminating a user operation provided by an embodiment of the present invention. The execution subject of this embodiment may be a server, and this embodiment is not particularly limited here. As shown in FIG1 , the method includes:

S101: Monitor the service call triggered by the user's operation in the distributed system, and create a call chain context object for the service call.

In this embodiment, before monitoring the service call triggered by the user operation, the following steps are also included: receiving the user's login identity authentication information, and generating an encrypted string based on the login identity authentication information; verifying the user's identity based on the string, and if the verification passes, executing the user operation to trigger the service call; if the verification fails, sending a notification of verification failure to the user end.

Specifically, when a user accesses a distributed system, he or she must first perform login authentication. The login authentication method can be: receiving the user's login authentication information, generating an encrypted token string based on the login authentication information, and then passing the token string to the background ajax interface for each subsequent operation to indicate his or her identity. After receiving the token string, the background ajax interface verifies the user's identity based on the token string. If the verification is successful, the user logs in to the distributed system and triggers a service call through the operation; if the verification fails, the user cannot log in to the distributed system, and a notification of failed verification can be sent to the user end to remind the user of the login failure.

In this embodiment, after monitoring the service call triggered by the user operation, the following steps are also included: obtaining the user's request header field; and decrypting the request header field to obtain the user identity information.

Specifically, the user's request header field may be: header.token.staffNo or service.param.staffNo|service.name=com.xxx.order.Create. After monitoring the service call triggered by the user operation, the user identity information is decrypted according to the user's request header field. In this embodiment, the user identity information may be a staff number code, and the attribute name of the staff number code is staffNo.

In this embodiment, the service call includes one or more of the following: calling an ajax interface, executing a local java method, executing an asynchronous thread, sending an asynchronous message, scheduling a timed task, calling a remote service, and accessing a database.

In this embodiment, the specific steps of monitoring the service call triggered by the user operation and creating a call chain context object for the service call include:

When the call chain context transfer module monitors the employee calling the ajax interface, it first decrypts the employee identity information according to the request header field token. In this embodiment, the employee identity information is the employee number code, and the attribute name is staffNo. The call chain context transfer module creates a call chain context object for this ajax call and saves the employee number code in the context object. In addition, the context object also saves the unique number of the call chain and each service node that the call chain has passed through. When this ajax interface involves calling other services, the call chain context object will continue to be passed.

S102: Save the user identity information in the call chain context object, so that the user identity information can be transmitted on the distributed call chain.

In this embodiment, the user identity information is saved in the call chain context object, and the user identity information is kept transmitted on the distributed call chain, which can facilitate the subsequent determination of whether the service call triggered by the user operation needs to be intercepted, and the user identity information can be obtained from the call chain context object.

Specifically, the call chain context object also stores: the unique number of the distributed call chain and each service node that the distributed call chain passes through. The unique number of the distributed call chain can be used to distinguish and confirm different call chains in different distributed systems. Each service node that the distributed call chain passes through is all service nodes included in the service call triggered by the user operation.

S103: Acquire user identity information, intercept the executing service call triggered by the user identity information, and generate an interception identity information range.

In this embodiment, the specific steps of obtaining user identity information, intercepting the executing service call triggered by the user identity information, and generating the interception identity information range include:

Obtain user identity information; send an interception instruction and broadcast the interception instruction; intercept the executing service call triggered by the user identity information according to the interception instruction, and generate an interception identity information range.

Specifically, in this embodiment, the actions of obtaining user identity information, intercepting the service call being executed triggered by the user identity information, and generating the interception identity information range can be completed by the interception instruction sending module, and the interception instruction sending module can be a Web project with a graphical operation interface. The system security controller enters the interception instruction sending module and enters a user identity information, such as a work number code, to intercept the service call being executed triggered by the work number code, and display the interception details. The interception instruction sending module will provide a fixed connection port to all interception instruction execution modules, such as 10.10.10.10:36770. When the security controller wants to issue an interception instruction, it will first obtain the interception instruction execution module that is connected to the connection port, and broadcast it through the connection port: "KILL STAFF_NO 10010", which means that the service call being executed by the work number 10010 is to be intercepted, and the interception instruction execution module is continuously waiting to return the interception result list and display it on the page.

Among them, Web engineering refers to engineering that acquires and transmits information based on the network, allowing users to input information on the browser side, which is then transmitted to the server for processing to obtain the information the user wants and then returned to the user's browser side.

S104: Before the service is formally called, obtain the call chain context object, extract the user identity information from the call chain context object, and determine whether the user identity information is within the intercepted identity information range. If not, execute step S105; if so, execute step S106.

In this embodiment, this step can be completed by an interception instruction execution module, which can be deployed in the application process of the distributed system in the form of a Java probe, and can monitor the calling behavior of each service. Before the service is formally called, since the call chain context object stores the user identity information, the call chain context object is obtained, and the user identity information can be obtained from the call chain context object. By judging whether the user identity information is within the interception identity information range, it can be determined whether the service call triggered by the user's operation needs to be intercepted.

S105: Continue service calling.

In this embodiment, if the user identity information is not within the interception identity information range, it means that the service call triggered by the user's operation does not need to be intercepted, and the service call can continue.

S106: Terminate the service call and generate an abnormal signal and interception details.

In this embodiment, if the user identity information is within the interception identity information range, it means that the service call triggered by the user's operation needs to be intercepted, so the service call is terminated, and an exception signal is thrown to the upper-level method, and the exception is described as "staff forbidden". Finally, the HTTP protocol is used to report the details of this interception, including user identity information such as work number code, interception time, and terminated service call. An unexpected situation that occurs during the operation of a program is called an exception. An exception is a signal used by the caller to convey information, indicating that an unexpected situation has occurred in the program. Once an exception occurs during program operation, the program will terminate immediately, and the code after the exception cannot continue to execute. In order to maintain a robust system for the program and not terminate due to a small error, the exception needs to be handled, for example, an exception handling mechanism can be used to handle it.

Specifically, the interception identity information range can be saved synchronously in the local memory and disk of the interception instruction execution module. After the interception instruction execution module receives the interception instruction, it is first loaded into the memory for use, and asynchronous disk writing is performed in the background to prevent the loss of the interception identity information range data when the module is reloaded.

S107: receiving an abnormal signal and interception details, wherein the interception details include user identity information, interception time, and terminated service call.

In this embodiment, the user identity information, interception time, and terminated service call in the interception details can be used for subsequent review of the user operation.

In summary, the user operation termination method provided in this embodiment creates a call chain context object for the service call by monitoring the service call triggered by the user's operation in the distributed system; saves the user identity information in the call chain context object to keep the user identity information transmitted on the distributed call chain; obtains the user identity information, intercepts the executing service call triggered by the user identity information, and generates an interception identity information range; before the service is formally called, obtains the call chain context object, extracts the user identity information from the call chain context object, and if it is determined that the user identity information is not within the interception identity information range, continues the service call; if it is determined that the user identity information is within the interception identity information range, terminates the service call, and generates an abnormal signal and interception details; receives the abnormal signal and interception details, wherein the interception details include the user identity information, the interception time, and the terminated service call, thereby realizing the instant termination of the service call in the background flow of the distributed system.

FIG2 is a second flow chart of the user operation termination method provided by an embodiment of the present invention. Based on the embodiment provided by FIG1 , this embodiment adds a method for terminating a service call after the service is called. As shown in FIG2 , the method includes:

S201: After the service is called, a call chain context object is obtained, and user identity information is extracted from the call chain context object.

In this embodiment, this step can be completed by an interception instruction execution module, which can be deployed in the application process of the distributed system in the form of a Java probe, and can monitor the calling behavior of each service. After the service is called, since the call chain context object stores the user identity information, the call chain context object is obtained, and the user identity information can be obtained from the call chain context object. The user identity information can be used to determine whether the service call triggered by the user's operation needs to be intercepted.

S202: Determine whether the user identity information is within the intercepted identity information range, if not, execute step S202, if yes, execute step S203.

In this embodiment, by determining whether the user identity information is within the interception identity information range, it can be determined whether the service call triggered by the user's operation needs to be intercepted.

S203: Return the service processing result.

In this embodiment, if the user identity information is not within the interception identity information range, it means that the service call triggered by the user's operation does not need to be intercepted, and the service processing result can be returned after the service call is completed.

S204: The service termination processing result is returned, and an abnormal signal and interception details are generated.

In this embodiment, if the user identity information is within the interception identity information range, it means that the service call triggered by the user's operation needs to be intercepted, so the service processing result is terminated and returned, and an exception signal is thrown to the upper-level method. The exception is described as "staff forbidden", and finally the HTTP protocol is used to report the details of this interception, including user identity information such as work number code, interception time, and terminated service call.

S205: Receive an abnormal signal and interception details, wherein the interception details include user identity information, interception time, and terminated service calls.

In this embodiment, the user identity information, interception time, and terminated service call in the interception details can be used for subsequent review of the user operation.

In summary, the user operation termination method provided in this embodiment obtains the call chain context object after the service is called, extracts the user identity information from the call chain context object, and determines whether the user identity information is within the interception identity information range; if it is determined that the user identity information is not within the interception identity information range, the service processing result is returned; if it is determined that the user identity information is within the interception identity information range, the service processing result is terminated and returned, and an exception signal and interception details are generated; receiving the exception signal and interception details, the immediate termination of the called service in the distributed system is realized.

FIG3 is a flow chart of the user operation termination method provided by an embodiment of the present invention. This embodiment is a practical implementation of the user operation termination method in the present invention. As shown in FIG3 , the method includes:

S301: receiving the user's login identity authentication information, and generating an encrypted character string according to the login identity authentication information.

S302: Verify the identity of the user according to the character string. If the verification is successful, execute the user operation to trigger the service call; if the verification is not successful, send a notification of verification failure to the user end.

S303: Monitor the service call triggered by the user's operation in the distributed system, and create a call chain context object for the service call.

S304: Obtain the user's request header field, and decrypt the request header field to obtain the user identity information.

S305: Acquire user identity information, intercept the executing service call triggered by the user identity information, and generate an interception identity information range.

S306: Before the service is formally called or after the service is called, obtain the call chain context object, and extract the user identity information from the call chain context object.

S307: Determine whether the user identity information is within the intercepted identity information range, if not, execute step S308, if yes, execute step S309.

S308: Continue the service call or return the service processing result.

Specifically, before the service is formally called, the service call continues; after the service is called, the service processing result is returned.

S309: Terminate the service call or terminate the service processing result return, and generate an abnormal signal and interception details.

Specifically, before the service is formally called, the service call is terminated; after the service is called, the service processing result return is terminated.

S310: receiving an abnormal signal and interception details, wherein the interception details include user identity information, interception time, and terminated service calls.

In summary, the user operation termination method provided by the present embodiment receives the user's login identity authentication information, generates an encrypted string according to the login identity authentication information, verifies the user's identity according to the string, and if the verification is successful, executes the user operation to trigger the service call; if the verification fails, sends a notification of verification failure to the user end, monitors the service call triggered by the user's operation in the distributed system, creates a call chain context object for the service call; saves the user identity information in the call chain context object, so that the user identity information is kept transmitted on the distributed call chain; obtains the user identity information, intercepts the service call being executed triggered by the user identity information, and generates an interception intercept identity information range; before the service is formally called or after the service is called, obtain the call chain context object, extract the user identity information from the call chain context object, if it is determined that the user identity information is not within the intercept identity information range, continue the service call or return the service processing result; if it is determined that the user identity information is within the intercept identity information range, terminate the service call or terminate the service processing result return, and generate an abnormal signal and interception details; receive the abnormal signal and interception details, wherein the interception details include the user identity information, the interception time and the terminated service call, so as to realize the instant termination of the service before the formal call and the service after the call in the distributed system.

Fig. 4 is a schematic diagram of the structure of the user operation termination device provided by the embodiment of the present invention. As shown in Fig. 4, the user operation termination device includes: a monitoring module 401, a storage module 402, an interception module 403, an extraction module 404, a service calling module 405, a termination module 406 and a receiving module 407.

A monitoring module 401 is used to monitor the service call triggered by the user's operation in the distributed system and create a call chain context object for the service call;

A saving module 402 is used to save the user identity information in the call chain context object so that the user identity information can be transmitted on the distributed call chain;

The interception module 403 is used to obtain user identity information, intercept the executing service call triggered by the user identity information, and generate an interception identity information range;

The extraction module 404 is used to obtain the call chain context object before the service is formally called, extract the user identity information from the call chain context object, and determine whether the user identity information is within the interception identity information range;

The service calling module 405 is used to continue the service calling if it is determined that the user identity information is not within the intercepted identity information range;

The termination module 406 is used to terminate the service call and generate an abnormal signal and interception details if it is determined that the user identity information is within the interception identity information range;

The receiving module 407 is used to receive the abnormal signal and the interception details, wherein the interception details include the user identity information, the interception time and the terminated service call.

In a possible implementation, the user operation termination device also includes a verification module 408, which is used to receive the user's login identity authentication information, generate an encrypted string based on the login identity authentication information; verify the user's identity based on the string, and if the verification passes, execute the user operation to trigger the service call; if the verification fails, send a notification of verification failure to the user end.

In a possible implementation, the user operation termination device further includes a decryption module 409, which is used to obtain the user's request header field; and obtain the user identity information by decrypting the request header field.

In a possible implementation, the extraction module 404 is specifically used to obtain user identity information; send an interception instruction and broadcast the interception instruction; intercept the executing service call triggered by the user identity information according to the interception instruction, and generate an interception identity information range.

In one possible implementation, the user operation termination device also includes a return module 410, which is used to obtain a call chain context object after the service is called, extract user identity information from the call chain context object, and determine whether the user identity information is within the interception identity information range; if it is determined that the user identity information is not within the interception identity information range, return the service processing result; if it is determined that the user identity information is within the interception identity information range, terminate the service processing result return, and generate an abnormal signal and interception details; receive the abnormal signal and interception details, wherein the interception details include the user identity information, interception time, and the terminated service call.

In a possible implementation, the service call includes one or more of the following: calling an ajax interface, executing a local java method, executing an asynchronous thread, sending an asynchronous message, scheduling a timed task, calling a remote service, and accessing a database.

The user operation termination device provided in this embodiment can be used to execute the technical solution of the above-mentioned user operation termination method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

FIG5 is a schematic diagram of the hardware structure of a server provided by an embodiment of the present invention. As shown in FIG5 , the server of this embodiment includes: at least one processor 501 and a memory 502;

Memory 502, used to store computer-executable instructions;

The processor 501 is used to execute the computer-executable instructions stored in the memory to implement the various steps executed by the server in the above embodiment. For details, please refer to the relevant description in the above method embodiment.

Optionally, the memory 502 may be independent or integrated with the processor 501 .

When the memory 502 is independently configured, the server further includes a bus 503 for connecting the memory 502 and the processor 501 .

An embodiment of the present invention further provides a computer storage medium, in which computer execution instructions are stored. When a processor executes the computer execution instructions, the user operation termination method as described above is implemented.

An embodiment of the present invention further provides a computer program product, including a computer program. When the computer program is executed by a processor, the user operation termination method as described above is implemented.

An embodiment of the present invention further provides a computer program product, including a computer program. When the computer program is executed by a processor, the user operation termination method as described above is implemented.

In the several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, each module may exist physically separately, or two or more modules may be integrated into one unit. The above-mentioned module-composed unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the above-mentioned method in each embodiment of the present application.

It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic device or a main control device.

Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk, etc., various media that can store program codes.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims (10)

1. A user operation termination method, characterized by comprising: Monitor service calls triggered by user operations in the distributed system, and create a call chain context object for the service calls; The user identity information is stored in the call chain context object, so that the user identity information is kept transmitted on the distributed call chain; Obtaining user identity information, intercepting the executing service call triggered by the user identity information, and generating an interception identity information range; Before the service is formally called, the call chain context object is obtained, the user identity information is extracted from the call chain context object, and it is determined whether the user identity information is within the scope of the intercepted identity information; If it is determined that the user identity information is not within the intercepted identity information range, continue the service call; If it is determined that the user identity information is within the interception identity information range, the service call is terminated, and an abnormal signal and interception details are generated; The abnormal signal and the interception details are received, wherein the interception details include user identity information, interception time, and terminated service call. 2. The method according to claim 1, characterized in that before monitoring the service call triggered by the user operation, it also includes: Receive the user's login identity authentication information, and generate an encrypted string according to the login identity authentication information; The user's identity is verified according to the character string. If the verification is successful, the user operation is executed to trigger the service call; if the verification is not successful, a notification of verification failure is sent to the user end. 3. The method according to claim 1, characterized in that after monitoring the service call triggered by the user operation, it also includes: Get the user's request header field; The user identity information is obtained by decrypting the request header field. 4. The method according to claim 1, characterized in that the obtaining of user identity information, intercepting the executing service call triggered by the user identity information, and generating the interception identity information range comprises: Obtain user identity information; Sending an interception instruction, and broadcasting the interception instruction; The executing service call triggered by the user identity information is intercepted according to the interception instruction, and an interception identity information range is generated. 5. The method according to claim 1, characterized in that, after obtaining user identity information, intercepting the executing service call triggered by the user identity information, and generating the interception identity information range, it also includes: After the service is called, the call chain context object is obtained, the user identity information is extracted from the call chain context object, and it is determined whether the user identity information is within the scope of the intercepted identity information; If it is determined that the user identity information is not within the scope of intercepted identity information, the service processing result is returned; If it is determined that the user identity information is within the interception identity information range, the service processing result is terminated and returned, and an abnormal signal and interception details are generated; The abnormal signal and the interception details are received, wherein the interception details include user identity information, interception time, and terminated service call. 6. The method according to any one of claims 1 to 5 is characterized in that the service call includes one or more of the following: calling an ajax interface, executing a local java method, executing an asynchronous thread, sending an asynchronous message, scheduling a timed task, calling a remote service, and accessing a database. 7. A user operation termination device, characterized in that it comprises: A monitoring module, used to monitor the service calls triggered by user operations in the distributed system, and create a call chain context object for the service calls; A saving module, used to save the user identity information in the call chain context object, so that the user identity information can be kept transmitted on the distributed call chain; An interception module, used to obtain user identity information, intercept the executing service call triggered by the user identity information, and generate an interception identity information range; An extraction module, used for obtaining the call chain context object before the service is formally called, extracting the user identity information from the call chain context object, and determining whether the user identity information is within the scope of the intercepted identity information; A service calling module, configured to continue the service calling if it is determined that the user identity information is not within the intercepted identity information range; A termination module, configured to terminate the service call and generate an abnormal signal and interception details if it is determined that the user identity information is within the interception identity information range; The receiving module is used to receive the abnormal signal and the interception details, wherein the interception details include user identity information, interception time and terminated service call. 8. The device according to claim 7 is characterized in that it also includes: a verification module, which is used to receive the user's login identity authentication information, and generate an encrypted string based on the login identity authentication information; verify the user's identity based on the string, and if the verification passes, execute the user operation to trigger the service call; if the verification fails, send a notification of verification failure to the user end. 9. A server, comprising: a processor and a memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor executes the user operation termination method according to any one of claims 1 to 7. 10. A computer storage medium, characterized in that the computer storage medium stores computer execution instructions, and when a processor executes the computer execution instructions, the user operation termination method according to any one of claims 1 to 7 is implemented.