Login method, server device, client device, system and storage medium

By receiving the login request from the client device on the server device and sending commands to the virtual terminal, establishing a channel to realize simultaneous login between the host and the target container, and connecting to the permission system, the existing technology cannot support the login between the host and the container at the same time. The problem of this problem reduces login complexity and delay, and improves performance and security.

CN118944931APending Publication Date: 2024-11-12ALIPAY (HANGZHOU) INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411009099.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-25
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The prior art cannot support client devices to log in to the host and container at the same time, resulting in high login complexity and time delay, and cannot be integrated with the permission system.

Method used

The server device receives the login request from the client device, sends commands to the virtual terminal and establishes a channel, realizes login at the same time as the host and the target container, and performs permission checks on the external permission system to reduce the login complexity and delay.

Benefits of technology

The purpose of logging in to the host and the target container simultaneously is achieved, reducing the login complexity and delay, and improving the performance of software and hardware combination and the feasibility of secure and trusted communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118944931A_ABST
    Figure CN118944931A_ABST
Patent Text Reader

Abstract

The invention provides a login method, server equipment, client equipment, a system and a storage medium. The method comprises the following steps: receiving a first login request sent by the client equipment; wherein the first login request is used for requesting to log in a host machine and a target container; sending the first command and the second command to the virtual terminal; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container; wherein the first command is used for logging in the host machine, and the second command is used for logging in the target container; receiving a channel establishment message sent by the virtual terminal; a channel setup message is sent to the client device. In the description, a server device can receive a first login request sent by a client device, and log in a host machine and a target container based on the first login request. The purpose of logging in the host machine and the target container at the same time is achieved, the complexity of logging in the host machine and the target container is reduced, the logging-in time delay is reduced, and the performance of combining software and hardware is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] One or more embodiments of the present specification relate to the field of authentication service technology, and in particular, to a login method and a server device, a client device, a system, and a storage medium. Background Art

[0002] Currently, a client device can initiate a login request to log in to a host or a container, but the relevant technology does not support logging in to both the host and the container at the same time. Summary of the invention

[0003] In view of this, one or more embodiments of this specification provide the following technical solutions:

[0004] According to a first aspect of one or more embodiments of this specification, a login method is proposed, the method being executed by a server device, the method comprising:

[0005] Receive a first login request sent by a client device; wherein the first login request is used to request to log in to a host machine and a target container;

[0006] Sending a first command and a second command to a virtual terminal; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container; wherein the first command is used to log in to the host machine, and the second command is used to log in to the target container;

[0007] Receiving a channel establishment message sent by the virtual terminal; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established;

[0008] Send the channel establishment message to the client device.

[0009] According to a second aspect of one or more embodiments of this specification, a login method is proposed, the method being executed by a client device, the method comprising:

[0010] Sending a first login request to the server device; wherein the first login request is used to request to log in to the host machine and the target container;

[0011] Receive a channel establishment message sent by the server device; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container.

[0012] According to a third aspect of one or more embodiments of this specification, a server device is provided. The server device is deployed on a host machine, and the server device includes:

[0013] A first receiving module, configured to receive a first login request sent by a client device; wherein the first login request is used to request to log in to a host machine and a target container;

[0014] A first sending module, configured to send a first command and a second command to a virtual terminal; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container; wherein the first command is used to log in to the host machine, and the second command is used to log in to the target container;

[0015] A second receiving module is used to receive a channel establishment message sent by the virtual terminal; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established;

[0016] The second sending module is used to send the channel establishment message to the client device.

[0017] According to a fourth aspect of one or more embodiments of this specification, a client device is provided, wherein the client device includes:

[0018] A third sending module is used to send a first login request to the server device; wherein the first login request is used to request to log in to the host machine and the target container;

[0019] The third receiving module is used to receive a channel establishment message sent by the server device; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container.

[0020] According to a fifth aspect of one or more embodiments of this specification, a login system is provided, the system comprising:

[0021] A server device, used to execute the steps of the method as described in any one of the first aspects;

[0022] A client device, used to execute the steps of the method as described in any one of the second aspects.

[0023] According to the sixth aspect of one or more embodiments of this specification, an electronic device is proposed, comprising: a processor; a memory for storing processor executable instructions; wherein the processor implements the steps of the method described in any one of the first aspect or the second aspect by running the executable instructions.

[0024] According to a seventh aspect of one or more embodiments of the present specification, a computer-readable storage medium is proposed, on which computer instructions are stored, and when the instructions are executed by a processor, the steps of the method described in any one of the first aspect or the second aspect are implemented.

[0025] According to an eighth aspect of one or more embodiments of the present specification, a computer program product is proposed, comprising a computer program / instruction, which, when executed by a processor, implements the steps of the method described in any one of the first aspect or the second aspect.

[0026] As can be seen from the above embodiments, in this specification, the server device can receive the first login request sent by the client device, and log in to the host machine and the target container based on the first login request. The purpose of logging in to the host machine and the target container at the same time is achieved, the complexity of logging in to the host machine and the target container is reduced, the login delay is reduced, and the performance of the combination of software and hardware is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 It is a schematic diagram of the architecture of a login system provided by an exemplary embodiment.

[0028] Figure 2 This is one of the flowchart diagrams of a login method provided by an exemplary embodiment.

[0029] Figure 3 This is the second flowchart of a login method provided by an exemplary embodiment.

[0030] Figure 4 It is an interactive schematic diagram of a login method provided by an exemplary embodiment.

[0031] Figure 5 It is a schematic structural diagram of an electronic device provided by an exemplary embodiment.

[0032] Figure 6 It is a structural diagram of a server device provided by an exemplary embodiment.

[0033] Figure 7 It is a structural diagram of a client device provided by an exemplary embodiment. DETAILED DESCRIPTION

[0034] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Instead, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0035] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0036] Before introducing the technical solution of this specification, the nouns involved in this specification are first introduced.

[0037] Host machine: can refer to a collection of physical machines, cloud servers (Elastic Compute Service, ECS), and virtual machines (Virtual Manufacturing, VM).

[0038] Container: can refer to a collection of containers (Pod Container) managed by a container management platform such as K8S.

[0039] Login protocol: a protocol for logging into a host or container, represented by the Secure Shell (SSH) protocol, as well as commands executed in containers such as kubectl exec and docker exec.

[0040] Command channel: refers to the link provided to users and applications in the form of an application programming interface (API) for issuing and executing batch commands to the host and container.

[0041] Identity certificate: refers to the certificate type that carries user identity information.

[0042] Trusted tunnel: refers to the security reinforcement of the command channel link. The encrypted communication link is the security guarantee for the command issuance link.

[0043] Permission plug-in: refers to the functional module that controls the access rights of the login subject and object during the login process.

[0044] The goal of the Trust System Entrypoint (TSE) is to provide resource isolation and secure and reliable operation and maintenance capabilities in cloud-native scenarios. Drawing on mature experience in operation and maintenance control, command channels, etc., and taking container isolation technology as the core, the operation and maintenance channel capabilities are rethought and designed in cloud-native scenarios.

[0045] Container login solutions represented by kubectl and docker currently only solve the login problem in container scenarios and cannot support the login capability of the host machine where the container is located (such as ECS or VM).

[0046] Login solutions such as SSH can provide login capabilities for both the host and the container through the Secure Shell Daemon (SSHD) service. However, SSH login permission control can only be controlled through the Linux login shell (login shell) and cannot be connected to an external permission system. In addition, there are management costs such as SSH account passwords and private keys.

[0047] To support simultaneous login to the host and container, this manual provides the following login methods and server devices, client devices, systems, and storage media.

[0048] Figure 1 FIG. 1 is a schematic diagram of the architecture of a login system provided by an exemplary embodiment. Figure 1 As shown, the system may include but is not limited to at least one of the following:

[0049] Server device 101;

[0050] Client device 102.

[0051] In some embodiments, the TSE may adopt a client / server architecture, and accordingly, the system may be composed of a server device 101 and a client device 102 .

[0052] In some embodiments, the server device 101 may be deployed on a host machine so that the host machine and the target container can be subsequently simulated through software to obtain a virtualized terminal, thereby achieving the purpose of logging into the host and the target container at the same time.

[0053] In some embodiments, the server device 101 may receive a first login request sent by the client device 102. The first login request may be used to request to log in to the host machine and the target container.

[0054] Furthermore, the server device 101 can first establish a secure encrypted channel with the client device 102, such as through the Transport Layer Security (TLS) or Secure Socket Layer (SSL) protocol, to ensure the security of data transmitted between the server device 101 and the client device 102.

[0055] The server device 101 can also check the identity certificate included in the first login request to obtain user identity information, such as user ID, user name, login password and other information, and can send a permission check request to an external permission system, such as a permission management server, requesting to check the permission of the client device 102 to log in to the host machine and the target container.

[0056] In an example, the permission check request may include, but is not limited to, at least one of the following: the user identity information; the login behavior information; the host machine information; and the target container information.

[0057] The login behavior information is used to indicate that the client device 102 is performing a login behavior.

[0058] The information of the host machine may include but is not limited to the address of the host machine, the identifier of the host machine and other information.

[0059] The target container information may include but is not limited to the container name, container identifier and other information.

[0060] The above is only an exemplary description, and the present disclosure does not limit the information content included in the permission check request.

[0061] Furthermore, the server device 101 may receive the permission check result returned by the permission management server.

[0062] If the permission check result indicates that the client device does not have the permission to log in to the host machine and / or the target container, the server device 101 may send a login rejection message to the client device 102 .

[0063] If the permission check result indicates that the client device has the permission to log in to the host machine and the target container, the server device 101 sends a first command and a second command, wherein the first command is used to log in to the host machine, and the second command is used to log in to the target container.

[0064] Exemplarily, the first command may be a nsenter command, and the second command may be a docker attach command.

[0065] Furthermore, the server device 101 may receive a channel establishment message sent by a virtual terminal, wherein the virtual terminal is a virtualized terminal obtained by simulating the host machine and the target container through software.

[0066] The channel establishment message may be a pty tunnel message.

[0067] At this point, a channel has been established between the server device 101 and the virtual terminal, and the server device 101 can forward the channel establishment message to the client device 102, so that the client device 102 determines that the login is successful.

[0068] In some embodiments, the client device 102 may send a first login request to the server device 101 , and determine that the login is successful after receiving a channel establishment message sent by the server device 101 .

[0069] In the above embodiment, the server device can receive the first login request sent by the client device, and log in to the host machine and the target container based on the first login request. The purpose of logging in to the host machine and the target container at the same time is achieved, and the permission system can be externally connected, which improves the feasibility of secure and trusted communication.

[0070] Figure 2 FIG. 1 is a flowchart of a login method provided by an exemplary embodiment. Figure 2 As shown, the method can be executed by the above-mentioned server device 101, and the method can include the following steps:

[0071] Step 201 : receiving a first login request sent by the client device 102 .

[0072] In some embodiments, the first login request is used to request to log into the host machine and the target container.

[0073] In some embodiments, the first login request may include, but is not limited to, at least one of the following: information of the host machine, information of the target container, an identity certificate, and the like.

[0074] Step 202: Send a first command and a second command to the virtual terminal based on the first login request.

[0075] In some embodiments, the virtual terminal is a virtualized terminal obtained by performing terminal simulation on the host machine and the target container that the client device 102 requests to log in.

[0076] In some embodiments, the server device 101 may send a first command to the virtual terminal, and send a second command to the virtual terminal, wherein the first command is used to log in to the host machine, and the second command is used to log in to the target container.

[0077] In some embodiments, the first command may be a nsenter command, and the second command may be a docker attach command.

[0078] Step 203: Receive a channel establishment message sent by the virtual terminal.

[0079] In some embodiments, after successfully logging into the virtual terminal, a channel establishment message sent by the virtual terminal is received. Since the virtual terminal is a virtualized terminal corresponding to both the host machine and the target container, successfully logging into the virtual terminal means successfully logging into the host machine and the target container.

[0080] In one example, the channel establishment message of the client device may be a pty tunnel message.

[0081] Step 204 : Send the channel establishment message to the client device 102 .

[0082] In some embodiments, the server device 101 forwards the channel establishment message to the client device 102 so that the client device 102 can determine that the login is successful.

[0083] In the above embodiment, the server device can receive the first login request sent by the client device, and log in to the host machine and the target container based on the first login request. The purpose of logging in to the host machine and the target container at the same time is achieved, the complexity of logging in to the host machine and the target container is reduced, the login delay is reduced, and the performance of the combination of software and hardware is improved.

[0084] In some embodiments, after the server device 101 executes step 201 and receives the first login request, it can first establish a secure encrypted channel with the client device 102 .

[0085] The server device 101 may establish a secure encryption channel with the client device 102 based on SSL and / or TLS.

[0086] Furthermore, the server device 101 may check the identity certificate included in the first login request to determine the user identity information, such as the user name, user ID, login password and the like.

[0087] Furthermore, the server device 101 may send a permission check request to an external permission management server, requesting to check the permission of the client device 102 to log in to the host machine and the target container, and receive the permission check result returned by the permission management server.

[0088] If the permission check result indicates that the client device 102 has the permission to log in to the host machine and the target container, the server device 101 may continue to execute step 202 to send the first command and the second command.

[0089] If the permission check result indicates that the client device 102 does not have the permission to log in to the host machine and / or the target container, a login rejection message may be sent to the client device 102 .

[0090] In the above embodiment, the purpose of checking the login authority of the client device by connecting the server device to the authority management server is achieved, the security and reliability of logging into the host machine and the target container are improved, and the feasibility of secure and trusted communication is improved.

[0091] In some embodiments, the server device 101 can be deployed on a host node, thereby achieving the purpose of unified login to the host and the target container.

[0092] Figure 3 FIG. 1 is a flowchart of a login method provided by an exemplary embodiment. Figure 3 As shown, the method may be executed by the client device 102, and the method may include the following steps:

[0093] Step 301 : Send a first login request to the server device 101 .

[0094] In some embodiments, the first login request is used to request to log in to the host machine and the target container, wherein the first login request includes but is not limited to information of the host machine, information of the target container, an identity certificate, and the like.

[0095] Step 302 , receiving a channel establishment message sent by the server device 101 .

[0096] In some embodiments, the channel establishment message is used to indicate that a channel between the virtual terminal and the server device 101 has been established; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container.

[0097] In the above embodiment, the purpose of logging into the host machine and the target container at the same time is achieved, and the feasibility of secure and trusted communication is improved.

[0098] The above process is further illustrated below with examples.

[0099] In some embodiments, for example Figure 1 As shown in the figure, a C / S architecture can be adopted. Simply deploy the server on the host node to provide unified login for the host and container. Users can provide command line tools to directly log in to the host and container.

[0100] In some embodiments, the traditional SSH login protocol may not be used, but a unified login protocol based on the World Wide Web Socket (websocket) is provided for the host and container login scenarios. The protocol supports TLS and / or SSL encryption at the link layer, and supports the ability to connect to an external permission system in the interactive protocol. The involved protocols are shown in Table 1.

[0101] Table 1

[0102]

[0103]

[0104] In some embodiments, for example Figure 4 As shown, the login method includes the following steps:

[0105] Step 401: The client device sends a login request to the server device.

[0106] Step 402: The server device (deployed on the host node) performs TLS / SSL detection to establish a secure encrypted channel with the client device.

[0107] Step 403: The server device performs an identity certificate check.

[0108] Step 404: The server device sends the user name, behavior, and target access control entry (ACI) to the authority system (eg, authority management server) for inspection.

[0109] Step 405: The authority system returns the check result.

[0110] If the user has the permission to log in to the target, then execute step 406; otherwise, execute step 409.

[0111] Step 406: The server sends a request to the host and the target container ( Figure 4 The virtual terminal (also called the target) sends nsenter commands and / or docker attach commands.

[0112] Step 407, the target returns to the pty tunnel.

[0113] Step 408: The server device returns the pty tunnel to the client device.

[0114] Step 409: The server device returns a login rejection message to the client device.

[0115] In the above embodiment, the server device can receive the first login request sent by the client device, and log in to the host machine and the target container based on the first login request. The purpose of logging in to the host machine and the target container at the same time is achieved, and the permission system can be externally connected, which improves the feasibility of secure and trusted communication.

[0116] Figure 5 is a schematic structural diagram of an electronic device provided by an exemplary embodiment. Figure 5At the hardware level, the device includes a processor 502, an internal bus 504, a network interface 506, a memory 508, and a non-volatile memory 510, and may also include hardware required for other functions. One or more embodiments of this specification may be implemented based on software, such as the processor 502 reading the corresponding computer program from the non-volatile memory 510 into the memory 508 and then running it. Of course, in addition to the software implementation, one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0117] Please refer to Figure 6 , the server device can be used for Figure 5 The electronic device shown in the figure, the server device is deployed on the host machine to implement the technical solution of this specification. Among them, the server device may include:

[0118] A first receiving module 601 is used to receive a first login request sent by a client device; wherein the first login request is used to request to log in to the host machine and the target container;

[0119] A first sending module 602 is used to send a first command and a second command to a virtual terminal; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container; wherein the first command is used to log in to the host machine, and the second command is used to log in to the target container;

[0120] The second receiving module 603 is used to receive a channel establishment message sent by the virtual terminal; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established;

[0121] The second sending module 604 is configured to send the channel establishment message to the client device.

[0122] Please refer to Figure 7 , the client device can be used for Figure 5 The electronic device shown in the figure is used to implement the technical solution of this specification. Among them, the client device may include:

[0123] The third sending module 701 is used to send a first login request to the server device; wherein the first login request is used to request to log in to the host machine and the target container;

[0124] The third receiving module 702 is used to receive a channel establishment message sent by the server device; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container.

[0125] Based on the same concept as the above method, this specification also provides a computer-readable storage medium on which computer instructions are stored. When the instructions are executed by a processor, the steps of the method described in any of the above embodiments are implemented.

[0126] Based on the same concept as the above method, this specification also provides a computer program product, including a computer program / instruction, which implements the steps of the method described in any of the above embodiments when executed by a processor.

[0127] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0128] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0129] It should be understood that, although the terms target, second, third, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the target information may also be referred to as the second information, and similarly, the second information may also be referred to as the target information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0130] The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.

Claims

1. A login method, It is characterized in that The method is executed by a server device, and the server device is deployed on a host machine. The method includes: Receive a first login request sent by a client device; wherein the first login request is used to request to log in to the host machine and the target container; Sending a first command and a second command to a virtual terminal; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container; wherein the first command is used to log in to the host machine, and the second command is used to log in to the target container; Receiving a channel establishment message sent by the virtual terminal; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established; Send the channel establishment message to the client device.

2. The method according to claim 1, It is characterized in that The server device is connected to the rights management server.

3. The method according to claim 2, It is characterized in that The method further comprises: Sending a permission check request to the permission management server; wherein the permission check request is used to request a check on the permission of the client device to log in to the host machine and the target container; Receive the permission check result sent by the permission management server.

4. The method according to claim 3, It is characterized in that The sending of the first command and the second command to the virtual terminal includes: If the permission check result provided by the permission management server indicates that the client device has the permission to log in to the host machine and the target container, the first command and the second command are sent to the virtual terminal.

5. The method according to claim 3, It is characterized in that The method further comprises: If the permission check result indicates that the client device does not have permission to log in to the host machine and / or the target container, a login rejection message is sent to the client device.

6. The method according to claim 3, It is characterized in that The permission check request includes at least one of the following: User identity information; Login behavior information; Information of the host machine; Information about the target container.

7. The method according to any one of claims 1 to 6, It is characterized in that After receiving the first login request sent by the client device, the method further includes: Establishing a secure encrypted channel with the client device; The identity certificate included in the first login request is checked to determine the user identity information.

8. A login method, It is characterized in that The method is performed by a client device, and the method includes: Sending a first login request to the server device; wherein the first login request is used to request to log in to the host machine and the target container; Receive a channel establishment message sent by the server device; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container.

9. The method according to claim 8, It is characterized in that The method further comprises: When the client device does not have permission to log in to the host machine and / or the target container, a login rejection message sent by the server device is received.

10. A server device, It is characterized in that The server device is deployed on a host machine, and the server device includes: A first receiving module, configured to receive a first login request sent by a client device; wherein the first login request is used to request to log in to the host machine and the target container; A first sending module, configured to send a first command and a second command to a virtual terminal; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container; wherein the first command is used to log in to the host machine, and the second command is used to log in to the target container; A second receiving module is used to receive a channel establishment message sent by the virtual terminal; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established; The second sending module is used to send the channel establishment message to the client device.

11. A client device, It is characterized in that The client device comprises: A third sending module is used to send a first login request to the server device; wherein the first login request is used to request to log in to the host machine and the target container; The third receiving module is used to receive a channel establishment message sent by the server device; wherein the channel establishment message is used to indicate that a channel between the virtual terminal and the server device has been established; wherein the virtual terminal is a virtualized terminal corresponding to the host machine and the target container.

12. A login system, It is characterized in that The system comprises: A server device, configured to execute the steps of the method according to any one of claims 1 to 7; A client device, configured to execute the steps of the method as claimed in any one of claims 8 or 9.

13. An electronic device, It is characterized in that include: processor; A memory for storing processor-executable instructions; wherein the processor implements the steps of the method as claimed in any one of claims 1-7 or 8-9 by running the executable instructions.

14. A computer-readable storage medium, It is characterized in that Computer instructions are stored thereon, and when the instructions are executed by a processor, the steps of the method as described in any one of claims 1-7 or 8-9 are implemented.