CN107395642B - Method and system for accessing and starting Docker container of TLS authentication based on Websocket - Google Patents
Method and system for accessing and starting Docker container of TLS authentication based on Websocket Download PDFInfo
- Publication number
- CN107395642B CN107395642B CN201710773166.0A CN201710773166A CN107395642B CN 107395642 B CN107395642 B CN 107395642B CN 201710773166 A CN201710773166 A CN 201710773166A CN 107395642 B CN107395642 B CN 107395642B
- Authority
- CN
- China
- Prior art keywords
- websocket
- docker container
- client
- connection
- unit
- 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 25
- 238000012544 monitoring process Methods 0.000 claims description 20
- 230000006854 communication Effects 0.000 claims description 16
- 238000004891 communication Methods 0.000 claims description 16
- 230000000977 initiatory effect Effects 0.000 claims description 7
- 230000007175 bidirectional communication Effects 0.000 claims description 5
- 230000003993 interaction Effects 0.000 claims description 5
- 230000006870 function Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Storage Device Security (AREA)
Abstract
The invention discloses a method and a system for accessing a Docker container for starting TLS authentication based on Websocket, belongs to the technical field of cloud computing, and solves the problem that in the prior art, the Docker container environment for starting TLS authentication cannot be directly established through an interface and a Websocket connection cannot be established and a Docker container cannot be accessed. The technical scheme is as follows: the method comprises the following steps: a user accesses a Web interface to initiate an access request; the Web interface starts a Websocket client to apply for a Websocket object to send a connection request; the Websocket server acquires a Websocket client connection request and queries the IP address of a host machine of a Docker container; the Websocket server loads a Docker container host TLS certificate file; generating a Docker container interface URL address through the IP address of the host and the Docker container ID; and establishing a Websocket connection, and opening a Web page containing a console terminal.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a method and a system for accessing and starting a Docker container of TLS authentication based on Websocket.
Background
Docker (Docker is a LXC-based advanced container engine that is an open source for the DotCloud of PaaS providers, with source code hosted on Github, open source based on the go language and compliant with the Apache2.0 protocol) is an open source application container engine that allows developers to package their applications and dependency packages into a portable container and then distribute it to any popular Linux machine.
Conventionally, to secure communications in a Docker container environment, the TLS protocol is typically used for encrypted transport (TLSTransport Layer Security is used to provide confidentiality and data integrity between two communicating applications). That is, by creating a self-signed certificate file and using a-TLS-verify command line option when running a Docker Daemon (Docker Daemon is a Daemon running in the background in the Docker container architecture), the server of the Docker container opens TLS authentication. Only clients that own the TLS key file can connect to the server of the Docker container. The server of the Docker container remains secure as long as the encrypted keys between the server and the client of the Docker container are secure. A key file is created on the server of the Docker container and distributed to trusted clients, and clients holding the key file can connect to the server of the Docker container.
WebSocket is a new protocol of HTML 5. The full duplex communication between the browser and the server is realized, server resources and bandwidth can be better saved, real-time communication is achieved, the full duplex communication is established on a TCP (transmission control protocol), data are transmitted through the TCP as HTTP, but the full duplex communication is different from HTTP in the greatest extent: the WebSocket is a two-way communication protocol, and after connection is established, the WebSocket server and the Browser/Client Agent can actively send or receive data to each other; WebSocket requires that a client side similar to TCP and a server side are connected through handshaking, and can communicate with each other only after the connection is successful.
The Docker container provides an interface to connect through websockets. However, in the Docker container environment where TLS authentication is started, it is impossible to establish a Websocket connection and access the Docker container directly through the interface.
Disclosure of Invention
The technical task of the invention is to provide a method and a system for accessing a Docker container for starting TLS authentication based on Websocket, so as to solve the problem that Websocket connection cannot be directly established and the Docker container cannot be accessed through the interface in the Docker container environment for starting TLS authentication in the prior art.
The technical task of the present invention is achieved in the following way,
the method for accessing the Docker container starting TLS authentication based on the Websocket comprises a Websocket client and a Websocket server; the method comprises the following steps:
(1) selecting a Docker container to be accessed and initiating an access request by a user through accessing a Web interface;
(2) the Web interface starts a Websocket client to apply for a Websocket object and sends a connection request;
(3) the Websocket server side starts a port monitoring request, acquires a Docker container ID transmitted by the Websocket client side after receiving a Websocket client side connection request, and queries a host machine IP address where the Docker container is located;
(4) loading a TLS certificate file of a host machine where the Docker container is located by the Websocket server;
(5) the Websocket server generates a URL address of a Docker container interface through a host machine IP address and the ID of the Docker container;
(6) the Websocket server establishes Websocket connection to the Docker container through the URL address of the Docker container interface and provides the Websocket connection for the Websocket client to use;
(7) and the Websocket client successfully establishes connection, and opens a Web page containing the console terminal for the user to use.
In the step (2), the request parameters of the Websocket object are the address and the port of the Websocket server and the ID of the Docker container.
And the TLS certificate file takes the Websocket server as an agent, establishes the connection between the Websocket client and the Docker container, and remotely enters the Docker container for starting TLS authentication.
A system for initiating TLS authenticated Docker containers based on Websocket access, comprising
① access request unit, which is used to select the Docker container to be accessed on the Web interface and initiate the access request;
② Websocket communication unit for providing information interaction and realizing bidirectional communication function;
the Websocket communication unit comprises a Websocket client and a Websocket server,
the Websocket client comprises a connection request unit,
the connection request unit is used for applying for a Websocket object and sending out a connection request by starting the Websocket client on a Web interface;
the Websocket server comprises a monitoring unit, a TLS authentication unit, an acquisition unit and a Websocket connection unit,
the monitoring unit is used for monitoring a connection request of the Websocket client, acquiring a Docker container ID transmitted by the Websocket client and inquiring a host machine IP address where the Docker container is located;
the TLS authentication unit loads a TLS certificate file of a host machine where the Docker container is located and is used for providing confidentiality and complete data access;
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring the IP address of a host machine and the ID of a Docker container to generate the URL address of a Docker container interface;
the Websocket connecting unit is used for establishing Websocket connection to the Docker container through the URL address of the Docker container interface and providing the Websocket connection for the Websocket client to use;
③ the Websocket client successfully establishes connection for opening a Web page containing a console terminal for a user to use.
The Websocket object request parameters applied by the connection request unit are Websocket server side addresses and ports and the ID of the Docker container.
Loading a TLS certificate file of a host machine where a Docker container is located through a Websocket server, using the Websocket server as an agent, establishing connection between a Websocket client and the Docker container, and entering the Docker container for starting TLS authentication remotely.
Compared with the prior art, the method and the system for starting the Docker container of TLS authentication based on WebSocket access have the following advantages:
1. according to the method and the system for starting the Docker container based on WebSocket access TLS authentication, the TLS certificate file of the host machine where the Docker container is located is loaded through the WebSocket server, the WebSocket server is used as a proxy, the connection between the WebSocket client and the Docker container is established, remote access to the Docker container for starting the TLS authentication is realized, any transformation on the Docker container is not needed, and the method and the system can be realized based on WebSocket connection;
2. loading a TLS certificate file of a host machine where the Docker container is located, wherein the TLS certificate file is used for providing confidentiality and complete data access, and the access security is improved;
3. the method and the system for starting the Docker container of TLS authentication based on WebSocket access have the characteristics of simplicity and convenience in use, reliability, good expansibility and the like, and have good popularization and use values.
Drawings
The invention is further described below with reference to the accompanying drawings.
Fig. 1 is a flow diagram of a method and system for accessing a Docker container for initiating TLS authentication based on WebSocket.
Detailed Description
A method for Web access to a Docker container of the present invention is described in detail below with reference to the drawings and the detailed description.
Example 1:
the invention discloses a method for accessing and starting a Docker container of TLS authentication based on Websocket, wherein the Websocket comprises a Websocket client and a Websocket server; the method comprises the following steps:
(1) selecting a Docker container to be accessed and initiating an access request by a user through accessing a Web interface;
(2) the Web interface starts a Websocket client to apply for a Websocket object and sends a connection request;
(3) the Websocket server side starts a port monitoring request, acquires a Docker container ID transmitted by the Websocket client side after receiving a Websocket client side connection request, and queries a host machine IP address where the Docker container is located;
(4) loading a TLS certificate file of a host machine where the Docker container is located by the Websocket server;
(5) the Websocket server generates a URL address of a Docker container interface through a host machine IP address and the ID of the Docker container;
(6) the Websocket server establishes Websocket connection to the Docker container through the URL address of the Docker container interface and provides the Websocket connection for the Websocket client to use;
(7) and the Websocket client successfully establishes connection, and opens a Web page containing the console terminal for the user to use.
Example 2:
the invention discloses a method for accessing and starting a Docker container of TLS authentication based on Websocket, wherein the Websocket comprises a Websocket client and a Websocket server; the method comprises the following steps:
(1) selecting a Docker container to be accessed and initiating an access request by a user through accessing a Web interface;
(2) the Web interface starts a Websocket client to apply for a Websocket object and sends a connection request;
(3) the Websocket server side starts a port monitoring request, acquires a Docker container ID transmitted by the Websocket client side after receiving a Websocket client side connection request, and queries a host machine IP address where the Docker container is located;
(4) loading a TLS certificate file of a host machine where the Docker container is located by the Websocket server;
(5) the Websocket server generates a URL address of a Docker container interface through a host machine IP address and the ID of the Docker container;
(6) the Websocket server establishes Websocket connection to the Docker container through the URL address of the Docker container interface and provides the Websocket connection for the Websocket client to use;
(7) and the Websocket client successfully establishes connection, and opens a Web page containing the console terminal for the user to use.
In step (2), the request parameters of the Websocket object are the Websocket server-side address and port and the ID of the Docker container.
Example 3:
the invention discloses a method for accessing and starting a Docker container of TLS authentication based on Websocket, wherein the Websocket comprises a Websocket client and a Websocket server; the method comprises the following steps:
(1) selecting a Docker container to be accessed and initiating an access request by a user through accessing a Web interface;
(2) the Web interface starts a Websocket client to apply for a Websocket object and sends a connection request;
(3) the Websocket server side starts a port monitoring request, acquires a Docker container ID transmitted by the Websocket client side after receiving a Websocket client side connection request, and queries a host machine IP address where the Docker container is located;
(4) loading a TLS certificate file of a host machine where the Docker container is located by the Websocket server;
(5) the Websocket server generates a URL address of a Docker container interface through a host machine IP address and the ID of the Docker container;
(6) the Websocket server establishes Websocket connection to the Docker container through the URL address of the Docker container interface and provides the Websocket connection for the Websocket client to use;
(7) and the Websocket client successfully establishes connection, and opens a Web page containing the console terminal for the user to use.
In step (2), the request parameters of the Websocket object are the Websocket server-side address and port and the ID of the Docker container.
And the TLS certificate file takes the Websocket server as an agent, establishes the connection between the Websocket client and the Docker container, and remotely enters the Docker container for starting TLS authentication.
Example 4:
the system for starting the Docker container of TLS authentication based on Websocket access comprises
① access request unit, which is used to select the Docker container to be accessed on the Web interface and initiate the access request;
② Websocket communication unit for providing information interaction and realizing bidirectional communication function;
the Websocket communication unit comprises a Websocket client and a Websocket server,
the Websocket client comprises a connection request unit,
the connection request unit is used for applying for a Websocket object and sending out a connection request by starting the Websocket client on a Web interface;
the Websocket server comprises a monitoring unit, a TLS authentication unit, an acquisition unit and a Websocket connection unit,
the monitoring unit is used for monitoring a connection request of the Websocket client, acquiring a Docker container ID transmitted by the Websocket client and inquiring a host machine IP address where the Docker container is located;
the TLS authentication unit loads a TLS certificate file of a host machine where the Docker container is located and is used for providing confidentiality and complete data access;
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring the IP address of a host machine and the ID of a Docker container to generate the URL address of a Docker container interface;
the Websocket connecting unit is used for establishing Websocket connection to the Docker container through the URL address of the Docker container interface and providing the Websocket connection for the Websocket client to use;
③ the Websocket client successfully establishes connection for opening a Web page containing a console terminal for a user to use.
Example 5:
the system for starting the Docker container of TLS authentication based on Websocket access comprises
① access request unit, which is used to select the Docker container to be accessed on the Web interface and initiate the access request;
② Websocket communication unit for providing information interaction and realizing bidirectional communication function;
the Websocket communication unit comprises a Websocket client and a Websocket server,
the Websocket client comprises a connection request unit,
the connection request unit is used for applying for a Websocket object and sending out a connection request by starting the Websocket client on a Web interface;
the Websocket server comprises a monitoring unit, a TLS authentication unit, an acquisition unit and a Websocket connection unit,
the monitoring unit is used for monitoring a connection request of the Websocket client, acquiring a Docker container ID transmitted by the Websocket client and inquiring a host machine IP address where the Docker container is located;
the TLS authentication unit loads a TLS certificate file of a host machine where the Docker container is located and is used for providing confidentiality and complete data access;
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring the IP address of a host machine and the ID of a Docker container to generate the URL address of a Docker container interface;
the Websocket connecting unit is used for establishing Websocket connection to the Docker container through the URL address of the Docker container interface and providing the Websocket connection for the Websocket client to use;
③ the Websocket client successfully establishes connection for opening a Web page containing a console terminal for a user to use.
The Websocket object request parameters applied by the connection request unit are Websocket server side addresses and ports and the ID of the Docker container.
Example 6:
the system for starting the Docker container of TLS authentication based on Websocket access comprises
① access request unit, which is used to select the Docker container to be accessed on the Web interface and initiate the access request;
② Websocket communication unit for providing information interaction and realizing bidirectional communication function;
the Websocket communication unit comprises a Websocket client and a Websocket server,
the Websocket client comprises a connection request unit,
the connection request unit is used for applying for a Websocket object and sending out a connection request by starting the Websocket client on a Web interface;
the Websocket server comprises a monitoring unit, a TLS authentication unit, an acquisition unit and a Websocket connection unit,
the monitoring unit is used for monitoring a connection request of the Websocket client, acquiring a Docker container ID transmitted by the Websocket client and inquiring a host machine IP address where the Docker container is located;
the TLS authentication unit loads a TLS certificate file of a host machine where the Docker container is located and is used for providing confidentiality and complete data access;
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring the IP address of a host machine and the ID of a Docker container to generate the URL address of a Docker container interface;
the Websocket connecting unit is used for establishing Websocket connection to the Docker container through the URL address of the Docker container interface and providing the Websocket connection for the Websocket client to use;
③ the Websocket client successfully establishes connection for opening a Web page containing a console terminal for a user to use.
The Websocket object request parameters applied by the connection request unit are Websocket server side addresses and ports and the ID of the Docker container.
Loading a TLS certificate file of a host machine where a Docker container is located through a Websocket server, using the Websocket server as an agent, establishing connection between a Websocket client and the Docker container, and entering the Docker container for starting TLS authentication remotely.
The present invention can be easily implemented by those skilled in the art from the above detailed description. It should be understood, however, that the present invention is not limited to the 6 specific embodiments described above. On the basis of the disclosed embodiments, a person skilled in the art can combine different technical features at will, thereby implementing different technical solutions.
In addition to the technical features described in the specification, the technology is known to those skilled in the art.
Claims (6)
1. The method for accessing and starting the Docker container of TLS authentication based on Websocket is characterized in that the Websocket comprises two components, namely a Websocket client and a Websocket server; the method comprises the following steps:
(1) selecting a Docker container to be accessed and initiating an access request by a user through accessing a Web interface;
(2) the Web interface starts a Websocket client to apply for a Websocket object and sends a connection request;
(3) the Websocket server side starts a port monitoring request, acquires a Docker container ID transmitted by the Websocket client side after receiving a Websocket client side connection request, and queries a host machine IP address where the Docker container is located;
(4) loading a TLS certificate file of a host machine where the Docker container is located by the Websocket server;
(5) the Websocket server generates a URL address of a Docker container interface through a host machine IP address and the ID of the Docker container;
(6) the Websocket server establishes Websocket connection to the Docker container through the URL address of the Docker container interface and provides the Websocket connection for the Websocket client to use;
(7) and the Websocket client successfully establishes connection, and opens a Web page containing the console terminal for the user to use.
2. The method for starting a Docker container of TLS authentication based on Websocket access as claimed in claim 1, wherein in step (2), the request parameters of the Websocket object are the Websocket server side address and port and the ID of the Docker container.
3. The method for accessing and starting a Docker container of TLS authentication based on Websocket as claimed in claim 1, wherein the method comprises loading a TLS certificate file of a host where the Docker container is located through a Websocket server, using the Websocket server as a proxy, establishing connection between the Websocket client and the Docker container, and entering the Docker container for starting TLS authentication remotely.
4. A system for accessing a Docker container for starting TLS authentication based on Websocket, characterized by comprising
① access request unit, which is used to select the Docker container to be accessed on the Web interface and initiate the access request;
② Websocket communication unit for providing information interaction and realizing bidirectional communication function;
the Websocket communication unit comprises a Websocket client and a Websocket server,
the Websocket client comprises a connection request unit,
the connection request unit is used for applying for a Websocket object and sending out a connection request by starting the Websocket client on a Web interface;
the Websocket server comprises a monitoring unit, a TLS authentication unit, an acquisition unit and a Websocket connection unit,
the monitoring unit is used for monitoring a connection request of the Websocket client, acquiring a Docker container ID transmitted by the Websocket client and inquiring a host machine IP address where the Docker container is located;
the TLS authentication unit loads a TLS certificate file of a host machine where the Docker container is located and is used for providing confidentiality and complete data access;
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring the IP address of a host machine and the ID of a Docker container to generate the URL address of a Docker container interface;
the Websocket connecting unit is used for establishing Websocket connection to the Docker container through the URL address of the Docker container interface and providing the Websocket connection for the Websocket client to use;
③ the Websocket client successfully establishes connection for opening a Web page containing a console terminal for a user to use.
5. The system for starting a Docker container for TLS authentication based on Websocket access as claimed in claim 4, wherein the Websocket object request parameters applied by the connection request unit are the Websocket server side address and port and the ID of the Docker container.
6. The system for accessing and starting a Docker container of TLS authentication based on Websocket as claimed in claim 4, wherein the system is characterized in that the Websocket server loads the TLS certificate file of the host where the Docker container is located, the Websocket server is used as a proxy to establish the connection between the Websocket client and the Docker container, and the Docker container for starting TLS authentication is entered remotely.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710773166.0A CN107395642B (en) | 2017-08-31 | 2017-08-31 | Method and system for accessing and starting Docker container of TLS authentication based on Websocket |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710773166.0A CN107395642B (en) | 2017-08-31 | 2017-08-31 | Method and system for accessing and starting Docker container of TLS authentication based on Websocket |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107395642A CN107395642A (en) | 2017-11-24 |
| CN107395642B true CN107395642B (en) | 2020-03-06 |
Family
ID=60347359
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710773166.0A Active CN107395642B (en) | 2017-08-31 | 2017-08-31 | Method and system for accessing and starting Docker container of TLS authentication based on Websocket |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107395642B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107948203B (en) * | 2017-12-29 | 2019-09-13 | 平安科技（深圳）有限公司 | A kind of container login method, application server, system and storage medium |
| CN108762893A (en) * | 2018-06-07 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of method, apparatus and storage medium of browser connection Docker containers |
| CN112532568B (en) * | 2019-09-19 | 2022-09-27 | 马上消费金融股份有限公司 | Interaction method, device, equipment and computer readable storage medium |
| CN110493269B (en) * | 2019-09-24 | 2021-09-07 | 福建中锐网络股份有限公司 | Method for Web remote Docker container desktop |
| CN112988333B (en) * | 2021-04-26 | 2021-09-03 | 武汉深之度科技有限公司 | Container application authentication method, system, computing device and readable storage medium |
| CN113468579A (en) * | 2021-07-23 | 2021-10-01 | 挂号网（杭州）科技有限公司 | Data access method, device, equipment and storage medium |
| CN114900719B (en) * | 2022-04-29 | 2024-01-30 | 广东博思信息技术股份有限公司 | Method and system for playing real-time video of monitoring equipment based on HTML5 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103582510A (en) * | 2010-12-10 | 2014-02-12 | 韦斯技术有限公司 | Methods and systems for accessing and controlling a remote desktop of a remote machine in real time by a web browser at a client device via HTTP API utilizing a transcoding server |
| CN105119913A (en) * | 2015-08-13 | 2015-12-02 | 东南大学 | Web server architecture based on Docker and interactive method between modules |
| CN106302448A (en) * | 2016-08-15 | 2017-01-04 | 中国联合网络通信集团有限公司 | remote access control method and device |
| CN106844000A (en) * | 2016-12-21 | 2017-06-13 | 北京大学 | Using the method and apparatus of browser access linux container cluster under a kind of multi-user environment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10348866B2 (en) * | 2016-02-19 | 2019-07-09 | Wuhan Mbaas Computing Co. Ltd. | Apparatus, system and method to provide IoT cloud backend service |
-
2017
- 2017-08-31 CN CN201710773166.0A patent/CN107395642B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103582510A (en) * | 2010-12-10 | 2014-02-12 | 韦斯技术有限公司 | Methods and systems for accessing and controlling a remote desktop of a remote machine in real time by a web browser at a client device via HTTP API utilizing a transcoding server |
| CN105119913A (en) * | 2015-08-13 | 2015-12-02 | 东南大学 | Web server architecture based on Docker and interactive method between modules |
| CN106302448A (en) * | 2016-08-15 | 2017-01-04 | 中国联合网络通信集团有限公司 | remote access control method and device |
| CN106844000A (en) * | 2016-12-21 | 2017-06-13 | 北京大学 | Using the method and apparatus of browser access linux container cluster under a kind of multi-user environment |
Non-Patent Citations (3)
| Title |
|---|
| ContainerSSh：基于WebSocket的Linux容器远程访问解决方案;赵培龙;《现代计算机（专业版）》;20160321;全文 * |
| Docker Daemon 连接方式详解;anyesu;《https://www.jianshu.com/p/7ba1a93e6de4》;20170630;全文 * |
| Docker服务中配置TLS;云开源;《https://www.sohu.com/a/158687705_468741》;20170720;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107395642A (en) | 2017-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107395642B (en) | Method and system for accessing and starting Docker container of TLS authentication based on Websocket | |
| EP2963884B1 (en) | Bidirectional authorization system, client and method | |
| US11075821B2 (en) | Method and apparatus for managing field device based on cloud server | |
| US20150188779A1 (en) | Split-application infrastructure | |
| CN104052746B (en) | Heterogeneous applications single-node login system and its single-point logging method | |
| CN108768979B (en) | Method for accessing intranet, device and system for accessing intranet | |
| CN105306433B (en) | A kind of method and apparatus accessing virtual machine server | |
| US20190281138A1 (en) | Connection Management Service | |
| CN105516171B (en) | Portal keep-alive system and method, Verification System and method based on authentication service cluster | |
| CN104767742A (en) | Safe communication method, gateway, network side server and system | |
| WO2015192582A1 (en) | Virtual desktop login authentication method and apparatus | |
| CN112165480A (en) | Information acquisition method and device and electronic equipment | |
| CN112507320A (en) | Access control method, device, system, electronic equipment and storage medium | |
| CN107294935B (en) | Virtual private network access method, device and system | |
| CN105518693A (en) | Safety protection method and device | |
| CN112583599B (en) | Communication method and device | |
| EP2800330A1 (en) | Secret key management method for multi-network platform | |
| US7457849B2 (en) | Controlled firewall penetration for management of discrete devices | |
| CN114301968B (en) | Access method, system, equipment and storage medium of server | |
| CN114422260B (en) | Cross-platform joint identity authentication method, system, storage medium and equipment | |
| CN111193776B (en) | Method, device, equipment and medium for automatically logging in client under cloud desktop environment | |
| EP3176986A1 (en) | Method, device and system for remote desktop protocol gateway to conduct routing and switching | |
| CN112118284A (en) | Gateway device-oriented http data request method, device and medium | |
| US20140325219A1 (en) | Secret key management method for multi-network platform | |
| CN115379008B (en) | Data transfer station system based on network server |
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 | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200520 Address after: 250100 No. 1036 Tidal Road, Jinan High-tech Zone, Shandong Province, S01 Building, Tidal Science Park Patentee after: Tidal Cloud Information Technology Co.,Ltd. Address before: 450000 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Patentee before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 250100 No. 1036 Tidal Road, Jinan High-tech Zone, Shandong Province, S01 Building, Tidal Science Park Patentee after: Inspur cloud Information Technology Co., Ltd Address before: 250100 No. 1036 Tidal Road, Jinan High-tech Zone, Shandong Province, S01 Building, Tidal Science Park Patentee before: Tidal Cloud Information Technology Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |