CN113568762B - Cross-system access method and device and computer readable storage medium thereof - Google Patents
Cross-system access method and device and computer readable storage medium thereof Download PDFInfo
- Publication number
- CN113568762B CN113568762B CN202110815488.3A CN202110815488A CN113568762B CN 113568762 B CN113568762 B CN 113568762B CN 202110815488 A CN202110815488 A CN 202110815488A CN 113568762 B CN113568762 B CN 113568762B
- Authority
- CN
- China
- Prior art keywords
- context
- login
- user
- cross
- program
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000006978 adaptation Effects 0.000 claims abstract description 44
- 230000004044 response Effects 0.000 claims abstract description 27
- 230000001960 triggered effect Effects 0.000 claims description 2
- 238000004891 communication Methods 0.000 abstract description 9
- 230000006870 function Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000003044 adaptive effect Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
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/54—Interprogram communication
- G06F9/543—User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a method for cross-system access, equipment and a computer readable storage medium thereof, wherein the method comprises the following steps: logging in a first system; obtaining a login context of the first system in response to successful login of the first system; calling an adaptation program to share the login context of the first system to the second system so as to log in the second system; wherein the first system and the second system are heterogeneous systems. Through the mode, the communication among the heterogeneous systems is realized, the function of calling the heterogeneous systems or the operation of the heterogeneous systems can be conveniently carried out after a user logs in one system, the cooperative working capacity of the heterogeneous systems is improved, the complicated switching among different systems by the user is avoided, and the working efficiency is improved.
Description
Technical Field
The present application relates to the field of access control technologies, and in particular, to a method for cross-system access, a device thereof, and a computer readable storage medium.
Background
Systems developed in different manners are generally called heterogeneous systems, for example, a micro service and OSGI system (Open SERVICE GATEWAY INITIATIVE, java-oriented dynamic model system) is a heterogeneous system, and heterogeneous systems can be used simultaneously and separately, but heterogeneous systems cannot access and operate mutually.
In the long-term research and development process, the inventor finds that under the condition that heterogeneous systems coexist, when a user uses one of the systems, the function and the like of the heterogeneous system are needed, but because the heterogeneous systems cannot be mutually accessed and operated, the user cannot use the function of the heterogeneous system through the system, so that the operation of the user on the cross-system is limited, and the use complexity of the user is increased.
Disclosure of Invention
The application mainly solves the technical problem of providing a cross-system access method, equipment and a computer readable storage medium thereof, which can realize the access and operation among heterogeneous systems.
In order to solve the technical problems, the application adopts a technical scheme that: a method of cross-system access is provided, the method comprising: logging in a first system; obtaining a login context of the first system in response to successful login of the first system; calling an adaptation program to share the login context of the first system to the second system so as to log in the second system; wherein the first system and the second system are heterogeneous systems.
Wherein after invoking the adaptation program to share the login context of the first system to the second system to login to the second system, the method further comprises: displaying a functional interface of the second system, wherein the functional interface is triggered to be displayed by a user performing a second operation on the first system; and responding to the first operation of the user on the functional interface of the second system, and sending a corresponding operation instruction to the second system.
The adapting program is arranged in the first system, displays a functional interface of the second system, and comprises the following steps: after logging in the second system, responding to a second operation of the user on the first system, and displaying a functional interface of the second system; or the adaptation program is arranged on the second system, after logging in the first system, and before calling the adaptation program to share the login context of the first system to the second system, the method further comprises: responding to a second operation of the user on the first system, and generating an access request to the second system; responding to the refusal information of the second system to the access request, executing the step of calling the adapting program to share the login context of the first system to the second system; after logging in the second system, a functional interface of the second system is displayed.
Wherein invoking the adaptation program to share the login context of the first system to the second system comprises: and calling a login subprogram of the adapting program to encapsulate the login context, and sending the encapsulated context to the second system.
Wherein after invoking the adaptation program to share the context of the first system to the second system to log in to the second system, the method further comprises: and in response to a third operation of the user on the first system, exiting the second system.
Wherein after invoking the adaptation program to share the login context of the first system to the second system to login to the second system, the method further comprises: in response to exiting the first system, generating an exit context of the first system, and invoking an adaptation program to share the exit context of the first system to the second system to exit the second system; or responding to the login account of the first system, generating a switching login context of the first system, and calling an adaptation program to share the switching login context of the first system to the second system so as to log in the second system by adopting the switched account; or re-logging on the first system in response to the timeout, generating a re-logging context of the first system, and invoking the adaptation program to share the re-logging context of the first system to the second system to re-log on the second system.
Wherein prior to logging into the first system, the method further comprises: the first system and the second system are registered in a registration center.
Wherein the first system is a micro-service and the second system is other systems than the micro-service.
In order to solve the technical problems, the application adopts another technical scheme that: there is provided a cross-system access device comprising a processor and a memory, the memory for storing program data, the processor for executing the program data to implement a method as in any one of the above.
In order to solve the technical problems, the application adopts another technical scheme that: there is provided a computer readable storage medium for storing program data executable to implement a method as in any one of the above.
In the scheme, the context of the first system is shared to the second system by calling the adaptive program, so that the context sharing is realized between the first system and the second system, the first system can be logged in to manage the second system, communication between heterogeneous systems is realized, and mutual access and operation between heterogeneous systems are realized, so that a user can log in to access the heterogeneous systems in one system, the function of the heterogeneous systems is convenient to use, the heterogeneous systems are convenient to operate, the cooperative working capacity of the heterogeneous systems is improved, complex switching between different systems by the user is avoided, and the working efficiency is improved.
Drawings
FIG. 1 is a flow diagram of one embodiment of a method of cross-system access of the present application;
FIG. 2 is a flow diagram of another embodiment of a method of cross-system access of the present application;
FIG. 3 is a flow diagram of yet another embodiment of a method of cross-system access of the present application;
FIG. 4 is a schematic diagram of a framework of one embodiment of a cross-system access device of the present application;
FIG. 5 is a schematic diagram of a framework of an embodiment of a computer readable storage medium of the present application.
Detailed Description
In order to make the objects, technical solutions and effects of the present application clearer and more specific, the present application will be described in further detail below with reference to the accompanying drawings and examples.
Referring to fig. 1, fig. 1 is a flow chart illustrating an embodiment of a method for cross-system access according to the present application. In this embodiment, the method is performed by a cross-system access device, which may be any device with processing capabilities, such as a computer, tablet, cell phone, etc. The method comprises the following steps:
Step S110: logging in a first system.
The cross-system access device in this embodiment is provided with clients of the first system and the second system, and may be responsive to user operations to initiate opening and logging in the first system or the second system, respectively. In particular, the first system and the second system may be applications such as a financial management system, a user centric service, a reporting center, etc. In general, a system developed in a different manner is referred to as a heterogeneous system, and in this embodiment, the first system and the second system are heterogeneous systems. In some embodiments, the first system may be a micro-service, the second system may be a system other than a micro-service, or the first system may be a system other than a micro-service, and the second system may be a micro-service. Of course, neither the first system nor the second system may have two heterogeneous systems other than the micro service, which is not limited herein.
It may be appreciated that the cross-system access device may log in to and access the first system through a client of the first system, and after logging in to the first system, the cross-system access device may display a functional interface fed back by the first background server on the client of the first system, so as to provide the user with the function of the first system. Similarly, the cross-system access device logs in and accesses the second system, and can log in and access a second background server associated with the second system through a client of the second system, and after logging in the second system, the cross-system access device can display a functional interface fed back by the second background server at the client of the second system so as to provide the user with the function of the second system to operate.
Step S120: in response to a successful login of the first system, a login context of the first system is obtained.
After the cross-system access device successfully logs in to the first system, a login context of the first system can be obtained, and the login context can be used for determining the legitimacy of the current login user. The login context may specifically include a user name, a password, a client or an IP address, etc.
Specifically, for example, the cross-system access device responds to a start operation of a user to a client of the first system, and displays a login interface of the first system; and responding to the account number and the password input by the user on the login interface, generating a login request of the first system, and sending the login request to the first background server. After verification is successful based on the account number and the password in the login request, the first background server determines that the cross-system access equipment successfully logs in the first system, generates return information after the login is successful, and sends the return information to the cross-system access equipment. The cross-system access device takes the return information as a login context for the first system.
Step S130: the adaptation program is called to share the login context of the first system to the second system so as to log in the second system.
The cross-system access device is provided with an adaptation program, which may in particular be located in a client of the first system or in a client of the second system. The adaptation program can realize the context sharing between the first system and the second system, for example, the adaptation program is used for packaging the context of the first system into information which can be identified by the second system, so that the second system can perform corresponding operations based on the context, such as synchronous login, synchronous exit and the like with the first system.
In a specific scenario, the cross-system access device invokes the adaptation program to encapsulate the login context of the first system, and shares the encapsulated login context to the second system, for example, the encapsulated login context is directly sent to a second background server associated with the second system, or sent to the second background server associated with the second system through a client of the second system, and the second background server verifies that the login user obtained by the first system is a legal user by using the login context, so that the user is allowed to log in the second system. The cross-system access device may switch from the first system to the functional interface of the second system to enable the user to operate the functions of the second system without requiring the user to log in to the second system.
According to the scheme, the context of the first system is shared to the second system by calling the adaptive program, so that the context sharing is realized between the first system and the second system, the second system can be managed by logging in the first system, communication between heterogeneous systems is realized, mutual access and operation between heterogeneous systems are realized, a user can log in and access the heterogeneous systems in one system, functions of the heterogeneous systems are convenient to use, the heterogeneous systems are convenient to operate, collaborative work capacity of the heterogeneous systems is improved, complex switching between different systems by the user is avoided, and work efficiency is improved.
Referring to fig. 2, fig. 2 is a flow chart illustrating another embodiment of a method for cross-system access according to the present application. In this embodiment, the method is performed by a cross-system access device, which may be any device with processing capabilities, such as a computer, tablet, cell phone, etc.
The method comprises the following steps:
step S210: the first system and the second system are registered in a registration center.
Before logging into the first system, the cross-system access device registers the first system and the second system with a registry, which may configure addresses of the registry for the first system and the second system to determine that the first system and the second system successfully register.
Step S220: logging in a first system.
Step S230: in response to a successful login of the first system, a login context of the first system is obtained.
Step S240: the adaptation program is called to share the login context of the first system to the second system so as to log in the second system. For a specific description of step S220, step S230 and step S240, reference is made to the above description about step S110, step S120 and step S130.
It will be appreciated that in some embodiments, a cross-system access device is provided with a configuration program that may be used to obtain addresses of backend servers of all systems of the registry. In a specific scenario, the configuration program is located in a client of the first system, and after the cross-system access device successfully logs in the first system, the configuration program is called to obtain addresses of background servers of other systems registered by a registration center of the first system, and part or all of the addresses of the background servers are saved as addresses of a second background server for use in subsequent steps.
In this embodiment, taking an example that the adaptation program is set at the client of the first system, after the cross-system access device opens and logs in the client of the first system and obtains the login context, the adaptation program set at the client of the first system may be directly called to share the login context of the first system to the second system.
In some embodiments, the first background server may generate multiple contexts and the second system may include multiple systems other than micro services, and the adaptation program may include multiple subroutines for synchronizing different types of contexts to different second systems. When the cross-system access device invokes the adaptation program, the corresponding sub-program is selected according to the context type and the second system type. Specifically, the adaptation program may include a login subroutine, an exit subroutine, a switch login subroutine, a timeout re-login subroutine, an exit subroutine, and the like.
In some embodiments, invoking the adaptation program to send the login context of the first system to the second system comprises: the cross-system access device invokes a login subroutine of the adaptation program to encapsulate the context of the first system, and the encapsulated login context is directly sent to the address of the second background server, or the encapsulated login context is sent to the address of the second background server through the client of the second system.
In a specific scenario, the login subroutine may include the following methods:
Step S250: and displaying a functional interface of the second system. After logging in the second system across the system access device, a functional page of the second system is displayed in response to a second operation of the user at the first system.
Specifically, after the cross-system access device is opened and logs in the first system in response to user operation, a functional interface fed back by the first background server is displayed. The cross-system access device may display the link of the second system in the form of an icon on the functional interface of the first system for the user to access the second system by clicking on the icon. And responding to the operation of clicking the icon of the second system by the user, opening the client side of the second system and displaying a functional interface fed back by the second background server by the cross-system access equipment so as to be operated by the user.
For example, the first system is a micro-service, in particular a user centric service, and the second system is an OSGI system (Open SERVICE GATEWAY INITIATIVE, java oriented dynamic model system), in particular an a-financial management system and a B-financial management system. Logging in the user center service through the cross-system access equipment, acquiring a logging context of the user center service sent by the first background server, and calling an adaptation program to share the logging context to the A financial management system and the B financial management system. After successfully logging in the user center service, displaying a functional interface of the user center service across the system access device, and displaying links of the A financial management system and the B financial management system in the functional interface of the user service center in the form of icons. The cross-system access device opens the A financial management system and displays a functional interface in response to a user clicking an entry button of the A financial management system.
Step S260: and responding to the first operation of the user on the functional interface of the second system, and sending a corresponding operation instruction to the second system.
And opening a client of the second system by the cross-system access equipment and displaying a functional interface fed back by the second background server so as to enable a user to operate the functions of the second system. The cross-system access device responds to the first operation of the user on the functional interface of the second system, and sends a corresponding operation instruction to the second background server to operate the second system, so that the cross-system access device accesses and operates the second system after logging in the first system.
Step S270: and in response to a third operation of the user on the first system, exiting the second system.
The cross-system access device may also exit the second system after logging into the second system. It will be appreciated that cross-system access may exit the first system and the second system simultaneously, or return to the first system after exiting the second system.
In some implementations, the cross-system access device may display a close icon at a functional interface of the first system or a functional interface of the second system, which may be used to exit the second system or to exit the first system and the second system. The following takes a cross-system access device to display a close icon on a functional interface of the first system, where the close icon is used for exiting the second system, and responding to a third operation of the user on the first system, the exiting the second system specifically includes: the cross-system access device obtains an exit context of the first system generated by the first background server in response to a third operation of the user on the first system, and the cross-system access device exits the second system based on the context.
Specifically, the cross-system access device deletes the first system login context stored locally in response to the exit context of the first system, so that a request of the cross-system access device to access the second system is rejected by the second backend server because the context verification is not passed, thereby exiting the second system from the cross-system access device. Or calling an exit subprogram by the cross-system access device to send the exit context of the first system to the second background server, deleting the login context of the first system by the second background server in response to the exit context, and verifying that the login user of the first system is an illegal user, thereby rejecting the user to access, so that the cross-system access device exits the second system.
The exit subprogram is used for sharing the exit context of the first system to the second system, and specifically, the exit subprogram is used for packaging the exit context of the first system into information which can be identified by the second system. For example, the exit subroutine may include the following methods:
According to the scheme in the embodiment, different subroutines are called for different types of second systems and context types, the context of the first system is shared to the second systems, so that the context sharing is realized between the first system and the second system, the first system can be logged in to manage the second system, meanwhile, the second system can be returned to the first system to continue to operate, communication among heterogeneous systems is realized, and therefore mutual access and operation among the heterogeneous systems are realized, so that a user can log in, access, operate and exit from the heterogeneous systems in one system, the functions of the heterogeneous systems are convenient to use, the operation is carried out on the heterogeneous systems, the cooperative working capacity of the heterogeneous systems is improved, complex switching among different systems by the user is avoided, and the working efficiency is improved.
Referring to fig. 3, fig. 3 is a flow chart illustrating a method for cross-system access according to another embodiment of the present application. In this embodiment, the method is performed by a cross-system access device, which may be any device with processing capabilities, such as a computer, tablet, cell phone, etc.
The method comprises the following steps:
Step S310: logging in a first system.
Step S320: in response to a successful login of the first system, a login context of the first system is obtained. For a specific description of step S310 and step S320, reference is made to the above description about step S220 and step S230.
In this embodiment, taking an example in which the adaptation program is provided on the client of the second system, the adaptation program cannot be directly called after logging in the first system across the system access device, and the adaptation program needs to be called by the second system.
Step S330: an access request to the second system is generated in response to a second operation of the user at the first system.
The cross-system access device responds to user operation to log in the first system, displays a functional interface fed back by the first background server at the client of the first system, and displays a link of the second system in the form of an icon on the functional interface of the first system so that the user can click the icon to access the second system.
It will be appreciated that the second system may comprise a number of systems registered with the registry. The cross-system access device may display links of several second systems in the form of icons on the functional interface of the first system, respectively. And the cross-system access equipment responds to the operation of clicking the icon by the user, and accesses the second system link corresponding to the icon.
Specifically, the cross-system access device generates an access request to the second system and sends the access request to the second background server in response to an operation of clicking the second system icon on the functional interface of the first system by the user. After receiving the access request, the second background server verifies that the login user of the first system is an illegal user by utilizing the context, and sends rejection information of the access request to the cross-system access equipment.
Step S340: and in response to the rejection information of the second system to the access request, calling the adaptation program to share the login context of the first system to the second system so as to log in the second system.
The cross-system access device receives refusal information of the access request sent by the second background server, an adaptation program is called to share the login context of the first system to the second system in response to the refusal information, the second background server verifies that the login user of the first system is a legal user by using the login context, and the permission of the user to login to the second system is determined, so that the cross-system access device can login to the second system.
For example, the first system is an OSGI system (Open SERVICE GATEWAY INITIATIVE, java-oriented dynamic model system), and may specifically be a financial management system, and the second system is a micro-service, and may specifically include a user center service, a reporting center, and the like. The cross-system access device logs in to the financial management system and receives a login context of the financial management system sent by the first background server. And displaying a functional interface of the financial management system across the system access equipment, and displaying links of micro services such as a user center service, a report center and the like of the second system in the form of icons on the functional interface of the financial management system so that the user can click the icons to access the second system. The cross-system access device generates an access request to the user center service in response to the user clicking the user center service icon, and sends the request to the second background server. And the second background server receives the access request sent by the cross-system access equipment, verifies that the user is an illegal user by utilizing the context and sends out rejection information. And the cross-system access equipment responds to the rejection information of the second background server, and invokes the adaptation program to synchronize the login context of the financial management system to the user center service, thereby logging in the user center service and displaying a functional interface of the user center service.
It can be understood that in this embodiment, the cross-system access device switches from the first system to the second system and displays the functional interface of the second system, and other systems of the same type as the second system may be displayed in the form of icons on the functional interface of the second system for the user to click the switch. For example, the second system is a micro-service, specifically including a user center service, a report center, and the like, after the cross-system access device logs in the user center service, the user responds to clicking a report center icon on a functional interface of the user center service, and the functional interface of the report center is displayed without returning to the financial management system to enter the report center.
By the method, the cross-system access equipment can be directly switched to other systems of the same type associated with the same registry through the second system, so that the jump process of accessing a plurality of second systems of the same type through the first system is simplified, and the working efficiency is improved.
It can be appreciated that after the cross-system access device logs in to the first system, the adapting program can be automatically invoked to share the context of the first system to the second system, and after the login context of the first system is shared to the second system, the cross-system access device can still display a functional interface of the first system for the user to operate the first system, for example, log out of the first system, switch the login account of the first system, or log in again over time. And responding to the operations of exiting the first system, switching the login account of the first system or overtime re-login, and the like, and correspondingly generating an exiting context, switching the login context or overtime re-login context by the first background server. The cross-system access device obtains the context of the first background system and shares the context to the second system to log in to the second system. Thus, in some embodiments, the method further comprises any of the following steps:
Step S350: and responding to the login account of the switched first system, generating a switched login context of the first system, and calling an adaptation program to share the switched login context of the first system to the second system so as to log in the second system by adopting the switched account.
Step S360: in response to the timeout, re-logging on the first system, generating a re-logging context for the first system, and invoking an adaptation program to share the re-logging context for the first system to the second system to re-log on the second system.
Step S370: in response to exiting the first system, an exit context for the first system is generated and an adaptation program is invoked to share the exit context for the first system to the second system to exit the second system.
In some embodiments, the cross-system access device logs in to the second system, displays a functional interface of the second system and a functional interface of the first system, and displays a close icon on the functional interface of the first system, where the icon is used to exit the first system and the second system, and the cross-system access device exits the first system in response to the user clicking the close icon and performs step S370.
The cross-system access device may be provided with an adaptation program, which may include a switch login sub-program, a timeout re-login sub-program, an exit sub-program, etc., for sharing different types of contexts.
The above steps S350, S360 and S370 are optional steps, and not performing the above steps does not affect cross-system access.
After the cross-system access device shares the context to the second system, the second backend server uses the context to verify that the new user is a legitimate user, thereby allowing the user to log into the second system.
According to the scheme in the embodiment, the context of the first system is shared to the second system by calling the adaptive program, so that the context sharing is realized between the first system and the second system, the second system can be managed by logging in the first system, the context of the first system can be shared when changed, communication among heterogeneous systems is realized, mutual access and operation among the heterogeneous systems are realized, a user can log in, access, operation and exit from the heterogeneous systems in one system, the functions of the heterogeneous systems are convenient to use, the cooperative working capacity of the heterogeneous systems is improved, complex switching among different systems by the user is avoided, and the working efficiency is improved.
Referring to fig. 4, fig. 4 is a schematic diagram of a cross-system access device according to an embodiment of the present application.
In this embodiment, the cross-system access device 40 includes a memory 41, a processor 42, and a man-machine interaction circuit 43, wherein the memory 41 and the man-machine interaction circuit 43 are respectively coupled to the processor 42. In particular, various components of cross-system access device 40 may be coupled together by a bus or processor 42 of cross-system access device 40 may be individually connected to other components.
The cross-system access device 40 may be a device in the foregoing embodiment, and specifically may be any device having processing capability, for example, a computer, a tablet computer, a mobile phone, and the like.
The memory 41 is used for storing program data executed by the processor 42 and data during processing by the processor 42. Such as program data of the first system, the second system, the adaptation program and the configuration program, the received context, etc. Wherein the memory 41 comprises a non-volatile storage portion for storing the above-mentioned program data.
The processor 42 controls the operation of the cross-system access device 40, the processor 42 may also be referred to as a CPU (central processing unit). The processor 42 may be an integrated circuit chip having signal processing capabilities. Processor 42 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. In addition, the processor 42 may be commonly implemented by a plurality of circuit-forming chips.
The processor 42 is operative to execute instructions to implement the steps of any of the method embodiments described above by invoking program data stored in the memory 41.
The man-machine interaction circuit 43 is used for displaying the functional interfaces of the first system and the second system and receiving the operation of the user on the functional interfaces.
For example, the processor 42 logs in to the first system, obtains a login context for the first system from the first background server in response to a successful login of the first system, and the processor 42 invokes the adaption routine to share the login context for the first system to the second background server to log in to the second system.
According to the scheme in the embodiment, the context of the first system is shared to the second system by calling the adaptive program, so that the context sharing is realized between the first system and the second system, the second system can be managed by logging in the first system, communication between heterogeneous systems is realized, mutual access and operation between heterogeneous systems are realized, a user can log in, access, operation and exit from the heterogeneous systems in one system, the function of the heterogeneous systems is convenient to use, the operation is carried out on the heterogeneous systems, the cooperative working capacity of the heterogeneous systems is improved, complex switching between different systems by the user is avoided, and the working efficiency is improved.
Referring to fig. 5, fig. 5 is a schematic diagram illustrating a framework of an embodiment of a computer readable storage medium according to the present application.
In this embodiment, the computer readable storage medium 50 stores program data 51 executable by a processor to implement any of the methods described above.
The computer readable storage medium 50 may be a medium such as a usb (universal serial bus), a removable hard disk, a Read-only memory (ROM), a random access memory (RAM, randomAccessMemory), a magnetic disk, or an optical disk, which may store program data, or may be a server storing the program data, and the server may send the stored program data to another device for running, or may also run the stored program data by itself.
In some implementations, the computer-readable storage medium 50 may also be a memory as shown in FIG. 4.
According to the scheme in the embodiment, the context of the first system is shared to the second system by calling the adaptive program, so that the context sharing is realized between the first system and the second system, the second system can be managed by logging in the first system, communication between heterogeneous systems is realized, mutual access and operation between heterogeneous systems are realized, a user can log in, access, operation and exit from the heterogeneous systems in one system, the function of the heterogeneous systems is convenient to use, the operation is carried out on the heterogeneous systems, the cooperative working capacity of the heterogeneous systems is improved, complex switching between different systems by the user is avoided, and the working efficiency is improved.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Claims (7)
1. A method of cross-system access, the method comprising:
logging in a first system;
obtaining a login context of the first system in response to successful login of the first system;
Displaying an access icon for accessing a second system and an exit icon for exiting the second system or for exiting the first system and the second system on a functional interface of the first system;
Calling an adaptation program to share the login context of the first system to a second system so as to log in the second system; wherein the first system and the second system are heterogeneous systems, and one of the first system and the second system is a micro service and the other is a system other than the micro service;
Displaying a functional interface of the second system, wherein the functional interface of the second system is triggered to be displayed through a second operation performed by a user on the first system, and the second operation is a clicking operation on the access icon;
Responding to a first operation of the user on a functional interface of the second system, and sending a corresponding operation instruction to the second system;
responding to a third operation of the user on the first system, exiting the second system, wherein the third operation is a clicking operation on the exiting icon;
responding to a login account for switching the first system, generating a switching login context of the first system, and calling the adaptation program to share the switching login context of the first system to a second system so as to log in the second system by adopting the switched account;
Responsive to a timeout, re-logging in the first system, generating a re-login context for the first system and invoking the adaptation program to share the re-login context for the first system to a second system to re-log in the second system;
In response to exiting the first system, an exit context for the first system is generated and the adaptation program is invoked to share the exit context for the first system to a second system to exit the second system.
2. The method of claim 1, wherein the adapting program is provided in the first system, and the displaying the functional interface of the second system comprises: after logging in the second system, responding to a second operation of a user on the first system, and displaying a functional interface of the second system;
Or the adaptation program is arranged on the second system, after logging in the first system, and before the calling adaptation program shares the login context of the first system to the second system, the method further comprises: generating an access request to the second system in response to a second operation of the user at the first system; responding to the refusal information of the second system to the access request, executing the step of calling the adapting program to share the login context of the first system to the second system; after logging in the second system, displaying a functional interface of the second system.
3. The method of claim 1, wherein the invoking the adaptation program to share the login context of the first system to a second system comprises:
And calling a login subprogram of the adaptation program to encapsulate the login context, and sending the encapsulated context to a second system.
4. The method of claim 1, wherein prior to the logging into the first system, the method further comprises:
registering the first system and the second system in a registration center.
5. The method of claim 1, wherein the first system is the micro-service and the second system is a system other than the micro-service.
6. A cross-system access device comprising a processor and a memory, the memory for storing program data, the processor for executing the program data to implement the method of any of claims 1-5.
7. A computer readable storage medium for storing program data, the program data being executable for implementing the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110815488.3A CN113568762B (en) | 2021-07-19 | 2021-07-19 | Cross-system access method and device and computer readable storage medium thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110815488.3A CN113568762B (en) | 2021-07-19 | 2021-07-19 | Cross-system access method and device and computer readable storage medium thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113568762A CN113568762A (en) | 2021-10-29 |
| CN113568762B true CN113568762B (en) | 2024-06-11 |
Family
ID=78165552
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110815488.3A Active CN113568762B (en) | 2021-07-19 | 2021-07-19 | Cross-system access method and device and computer readable storage medium thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113568762B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108241799A (en) * | 2018-01-31 | 2018-07-03 | 广州市全周至程软件技术有限公司 | cross-system access method, system, device and computer readable storage medium |
| CN109150913A (en) * | 2018-10-17 | 2019-01-04 | 东软集团股份有限公司 | Access method, apparatus, storage medium and the server of the application under micro services framework |
| CN109639723A (en) * | 2019-01-10 | 2019-04-16 | 深圳市买买提信息科技有限公司 | A kind of micro services access method and server based on ERP system |
| CN109672749A (en) * | 2019-01-07 | 2019-04-23 | 腾讯科技（深圳）有限公司 | Heterogeneous system intercommunication can intercommunication application method and apparatus |
| CN110048879A (en) * | 2019-03-12 | 2019-07-23 | 平安医疗健康管理股份有限公司 | Micro services register method, device, electronic equipment and computer readable storage medium |
| CN110971614A (en) * | 2019-12-17 | 2020-04-07 | 软通动力信息技术（集团）有限公司 | Internet of things adaptation method and system, computer equipment and storage medium |
| CN111859320A (en) * | 2020-06-22 | 2020-10-30 | 中国平安财产保险股份有限公司 | Cross-system login-free method, device, equipment and readable storage medium |
| CN112615849A (en) * | 2020-12-15 | 2021-04-06 | 平安科技（深圳）有限公司 | Micro-service access method, device, equipment and storage medium |
| CN112688937A (en) * | 2020-12-22 | 2021-04-20 | 武汉烽火众智数字技术有限责任公司 | Login method for system single sign-on under cross-application heterogeneous application |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10469497B2 (en) * | 2016-05-26 | 2019-11-05 | Dropbox, Inc. | Identifying accounts having shared credentials |
| US10574736B2 (en) * | 2017-01-09 | 2020-02-25 | International Business Machines Corporation | Local microservice development for remote deployment |
| US10764273B2 (en) * | 2018-06-28 | 2020-09-01 | Oracle International Corporation | Session synchronization across multiple devices in an identity cloud service |
-
2021
- 2021-07-19 CN CN202110815488.3A patent/CN113568762B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108241799A (en) * | 2018-01-31 | 2018-07-03 | 广州市全周至程软件技术有限公司 | cross-system access method, system, device and computer readable storage medium |
| CN109150913A (en) * | 2018-10-17 | 2019-01-04 | 东软集团股份有限公司 | Access method, apparatus, storage medium and the server of the application under micro services framework |
| CN109672749A (en) * | 2019-01-07 | 2019-04-23 | 腾讯科技（深圳）有限公司 | Heterogeneous system intercommunication can intercommunication application method and apparatus |
| CN109639723A (en) * | 2019-01-10 | 2019-04-16 | 深圳市买买提信息科技有限公司 | A kind of micro services access method and server based on ERP system |
| CN110048879A (en) * | 2019-03-12 | 2019-07-23 | 平安医疗健康管理股份有限公司 | Micro services register method, device, electronic equipment and computer readable storage medium |
| CN110971614A (en) * | 2019-12-17 | 2020-04-07 | 软通动力信息技术（集团）有限公司 | Internet of things adaptation method and system, computer equipment and storage medium |
| CN111859320A (en) * | 2020-06-22 | 2020-10-30 | 中国平安财产保险股份有限公司 | Cross-system login-free method, device, equipment and readable storage medium |
| CN112615849A (en) * | 2020-12-15 | 2021-04-06 | 平安科技（深圳）有限公司 | Micro-service access method, device, equipment and storage medium |
| CN112688937A (en) * | 2020-12-22 | 2021-04-20 | 武汉烽火众智数字技术有限责任公司 | Login method for system single sign-on under cross-application heterogeneous application |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113568762A (en) | 2021-10-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10397120B2 (en) | Service link selection control method and device | |
| CN112104754B (en) | Network proxy method, system, device, equipment and storage medium | |
| CN112653618B (en) | Gateway registration method and device of micro-service application API (application program interface) endpoint | |
| CN111193716B (en) | Service data calling method and device, computer equipment and storage medium | |
| US11831616B2 (en) | Reverse proxy servers for implementing application layer-based and transport layer-based security rules | |
| CN111163130B (en) | Network service system and data transmission method thereof | |
| CN111262839A (en) | Vulnerability scanning method, management equipment, node and storage medium | |
| US11595482B2 (en) | Image acquisition device virtualization for remote computing | |
| CN113326154B (en) | Connection management method, device, electronic equipment and storage medium | |
| US20200314133A1 (en) | Security Device Selection Based On Secure Content Detection | |
| WO2022100020A1 (en) | Vulnerability testing method and apparatus | |
| US20220398116A1 (en) | Application Virtualization System | |
| CN113568762B (en) | Cross-system access method and device and computer readable storage medium thereof | |
| CN117407195A (en) | Interface system, integration method and device of application system and third party system | |
| CN110673970A (en) | Cross-process calling system and method based on web application | |
| WO2023170653A1 (en) | System and method for providing multi factor authorization to rdp services through a zero trust cloud environment | |
| WO2023092316A1 (en) | Third-party service login method and apparatus, terminal device, and storage medium | |
| CN109451047A (en) | Data transferring method, device, equipment and the storage medium of monitoring warning system | |
| CN115604227B (en) | Communication control method and apparatus, communication system, and computer-readable storage medium | |
| CN112261051B (en) | User registration method, device and system | |
| CN110708180A (en) | Fault detection method, fault analysis method and device | |
| CN113157615B (en) | Service bus communication method, electronic equipment and computer storage medium | |
| US20230388296A1 (en) | System and method for providing rdp client based rdp services through a zero trust cloud environment | |
| CN107592229B (en) | Service calling method, device and system | |
| CN116723029A (en) | Access control method, device, equipment and storage medium |
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 | ||
| GR01 | Patent grant |