Communication system, information processing device, program, information processing method, and connector device
The communication system addresses VPN security challenges by using a cloud service with SSH authentication and WebSocket tunnels to secure remote work connections, enhancing security and simplifying VPN settings for companies.
Patent Information
- Application Number
- PCT/JP2023/018843
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-19
- Publication Date
- 2024-11-28
AI Technical Summary
Companies face challenges in securing their remote work VPN environments, including exposure to third-party attacks, complex VPN settings, and the risk of remote PCs being hacked, when setting up VPNs on-premises.
A communication system that uses a cloud service with a connector unit within the on-premises site and a reverse proxy unit to establish a WebSocket tunnel for secure communication, eliminating the need for traditional VPN devices and simplifying settings by using SSH authentication and public key encryption.
This solution enhances security by preventing unauthorized connections, encrypting communication data, and reducing the risk of third-party attacks without exposing global IP addresses, thus improving the overall security and accessibility for remote workers.
Smart Images

Figure JP2023018843_28112024_PF_FP_ABST
Abstract
Description
Communication system, information processing device, program, information processing method, and connector device
[0001] The present invention relates to a communication system, an information processing device, a program, an information processing method, and a connector device.
[0002] Patent Document 1 describes improving the security of remote work by connecting a company's information system with an employee's home line via a virtual private network (VPN). [Prior art documents] [Patent document 1] JP 2022-081071 A General disclosure
[0003] According to one embodiment of the present invention, there is provided a communication system. The communication system may include a connector unit disposed within an on-premises site. The communication system may include a service unit. The service unit may include a reverse proxy unit that communicates with the connector unit and a communication terminal via the Internet. The service unit may include a tunnel connection control unit that performs SSH authentication with the connector unit and, if the authentication is successful, creates a WebSocket tunnel between the reverse proxy unit and the connector unit. The service unit may include a client support unit that receives resource information within the on-premises site that corresponds to the connector unit via the WebSocket tunnel using encrypted communication and transmits the resource information to the communication terminal via the reverse proxy unit.
[0004] In the communication system, the client interface unit may perform the encrypted communication using SSH.
[0005] In the communication system, when the reverse proxy unit receives a connection request from the connector unit, the tunnel connection control unit may perform the SSH authentication with the connector unit, and if the authentication is successful, generate the WebSocket tunnel between the reverse proxy unit and the connector unit. When the reverse proxy unit receives a login request from the communication terminal to the service unit by a user of the communication terminal, the client corresponding unit may authenticate the user, and if the authentication is successful, receive the user's login information for the on-premises site from the communication terminal and send the login information to a directory server of the on-premises site via the WebSocket tunnel. When the client corresponding unit receives a request for a user server at the on-premises site from the communication terminal of the user whose login information has been successfully authenticated by the directory server, the client corresponding unit may access the file server at the on-premises site via the WebSocket tunnel to receive the resource information, convert the resource information into HTML data, and place the resource information on a web server of the client corresponding unit. Similarly, when the client corresponding unit receives a request to the web server of the on-premises site from the communication terminal of the user whose login information has been successfully authenticated by the directory server, it may access the web server of the on-premises site via the WebSocket tunnel to receive the resource information, convert the on-premises URL described in the HTML data in the resource information into a URL accessible from the communication terminal on the Internet, and place it on the web server of the client corresponding unit.
[0006] In the communication system, the connector unit may have a private key memory unit that stores a private key for SSH authentication, the tunnel connection control unit may have a public key memory unit that stores a public key corresponding to the private key, and the tunnel connection control unit and the connector unit may perform the SSH authentication using the private key and the public key. The communication terminal may have a terminal key memory unit that stores a public key corresponding to the private key, and when the client correspondence unit receives an SSH authentication request including the public key stored in the terminal memory unit from the communication terminal via the reverse proxy unit, the client correspondence unit may send the SSH authentication request to the connector unit via the WebSocket tunnel, and the connector unit may perform SSH authentication for the received SSH authentication request using the public key included in the SSH authentication request and the private key stored in the private key memory unit, and if the authentication is successful, may send success notification data to the client correspondence unit notifying that the authentication has been successful, and in response to receiving the success notification data, the client correspondence unit may request login information for the on-premises site of the user of the communication terminal from the communication terminal.
[0007] In the communication system, the tunnel connection control unit may include a private key storage unit that stores a private key for SSH authentication, the connector unit may include a public key storage unit that stores a public key corresponding to the private key, and the tunnel connection control unit and the connector unit may perform the SSH authentication using the private key and the public key. The communication terminal may include a terminal storage unit that stores a public key corresponding to the private key, and when the client support unit receives an SSH authentication request from the communication terminal via the reverse proxy unit, the client support unit may perform SSH authentication using the public key included in the SSH authentication request and the private key stored in the private key storage unit, and if the authentication is successful, the client support unit may request login information for the on-premises site of the user of the communication terminal from the communication terminal.
[0008] According to one embodiment of the present invention, there is provided an information providing device. The information providing device may include a reverse proxy unit that communicates with a communication terminal and a connector unit located within an on-premises site via the Internet. The information providing device may include a tunnel connection control unit that performs SSH authentication with the connector unit and, if the authentication is successful, creates a WebSocket tunnel between the reverse proxy unit and the connector unit. The information providing device may include a client support unit that receives resource information within the on-premises site corresponding to the connector unit via the WebSocket tunnel using encrypted communication and transmits the resource information to the communication terminal via the reverse proxy unit.
[0009] According to one embodiment of the present invention, there is provided a program for causing a computer to function as the information providing device.
[0010] According to one embodiment of the present invention, there is provided an information provision method executed by a computer. The information provision method may include a tunnel connection control step of performing SSH authentication with a connector unit located in an on-premises site via the Internet, and, if the authentication is successful, creating a WebSocket tunnel between the reverse proxy unit and the connector unit. The information provision method may include a receiving step of receiving resource information within the on-premises site corresponding to the connector unit via the WebSocket tunnel by encrypted communication. The information provision method may include a transmitting step of transmitting the resource information to a communication terminal via the Internet.
[0011] According to one embodiment of the present invention, there is provided a connector device. The connector device may include a private key storage unit that stores a private key for SSH authentication. The connector device may also include a connector unit that performs SSH authentication using the private key with a service unit located in a cloud via the Internet, and creates a WebSocket tunnel with the service unit if the authentication is successful.
[0012] The above summary of the invention does not list all of the necessary features of the present invention, and subcombinations of these features may also constitute inventions.
[0013] FIG. 1 is a schematic diagram illustrating an example of a communication system 10. FIG. 2 is an explanatory diagram illustrating processing in the communication system 10. FIG. 3 is a schematic diagram illustrating an example of the flow of processing in the communication system 10. FIG. 4 is an explanatory diagram illustrating processing in the communication system 10. FIG. 5 is a schematic diagram illustrating an example of the flow of processing in the communication system 10. FIG. 6 is an explanatory diagram illustrating processing in the communication system 10. FIG. 7 is a schematic diagram illustrating an example of the hardware configuration of a computer 1200 that functions as a service unit 100, a connector unit 300, or a communication terminal 400.
[0014] The present invention will be described below through embodiments of the invention, but the following embodiments do not limit the scope of the invention as claimed. Furthermore, not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.
[0015] 1 is a schematic diagram of an example of a communication system 10. The communication system 10 includes a service section 100 and a connector section 300.
[0016] For example, when a company sets up a VPN environment at an on-premises site for its remote employees, it faces several challenges. For example, it must consider the risk of exposing a global IP address to the Internet, exposing it to third-party attacks. For example, it must keep updating the VPN equipment to maintain security in preparation for attacks. For example, because remote PCs connect directly to the internal network, there is a high risk of the remote PCs being hacked. For example, it must deal with complex VPN settings.
[0017] In the communication system 10 according to this embodiment, the service unit 100 is realized as a cloud service. The connector unit 300 is located in an on-premise site 200 of a company or the like. The connector unit 300 and the reverse proxy unit 130 of the service unit 100 generate a WebSocket tunnel 180 to realize TCP (Transmission Control Protocol) / UDP (User Datagram Protocol) communication.
[0018] The service unit 100 communicates with the connector unit 300 via a WebSocket tunnel 180, and communicates with a communication terminal 400 of a user 40, such as an employee, via the Internet 20. The communication terminal 400 may be a smart device. The communication terminal 400 is, for example, a smartphone. The communication terminal 400 is, for example, a tablet terminal. The communication terminal 400 is, for example, a PC (Personal Computer).
[0019] The service unit 100 provides the communication terminal 400 of the user 40 with a remote connection environment to the on-premise site 200 without using a VPN device / VPN connection, enabling access to on-premise resources 220 such as a web portal, mail server, web application, file server, and file share within the on-premise site 200. This eliminates the need for a company to prepare a VPN environment for remote workers, and eliminates the burden of updating and operating the VPN device and complex VPN settings.
[0020] The service unit 100 includes a license management unit 110 , a client support unit 120 , a reverse proxy unit 130 , and a tunnel connection control unit 140 .
[0021] The license management unit 110 manages the contract status of service users for the cloud service provided by the service unit 100. The license management unit 110 manages, for example, information about companies that hold licenses. For example, the license management unit 110 manages the company that provided the connector unit 300 as a company that holds licenses.
[0022] The client support unit 120 may have a function to authenticate users 40 who wish to connect to the service unit 100. The client support unit 120 may manage information about users 40 registered by companies that have licenses for the cloud services provided by the service unit 100. The information about users 40 may include authentication information used to authenticate users 40. It may also include information about the communication terminal 400 of the user 40. When the user 40 connects to the service unit 100 using the communication terminal 400, the client support unit 120 refers to the managed information to confirm whether or not the user 40 can use the service.
[0023] The client correspondence unit 120 may have a function of authenticating a user 40 who wishes to access an on-premise resource 220 at the on-premise site 200. The client correspondence unit 120 may connect to a directory service or the like at the on-premise site 200 via a WebSocket tunnel 180 to authenticate the user 40.
[0024] The client association unit 120 performs authentication using, for example, a user ID and a password. The client association unit 120 may transmit the user ID and password received from the communication terminal 400 to a directory service of the on-premise site 200 and receive the authentication result. The client association unit 120 may use a universally unique identifier (UUID).
[0025] The client corresponding unit 120 may perform multi-factor authentication in combination with a one-time password. The client corresponding unit 120 may use a one-time password using email or SMS (Short Message Service). The client corresponding unit 120 may use a one-time password using a telephone. The client corresponding unit 120 may use a one-time password using an app. The client corresponding unit 120 may use a one-time password using a token. The client corresponding unit 120 may use a time-based one-time password (TOTP), a hash-based message authentication code one-time password (HOTP), or the like as the one-time password.
[0026] The client support unit 120 may provide the user 40 with a UI (User Interface) of the file server of the on-premise site 200. The client support unit 120 connects to the file server of the on-premise site 200 via the WebSocket tunnel 180 and converts the directory information of the file server into a Web interface (HTML) so that the user 40 can view, download, upload, and the like from the browser 410 of the communication terminal 400.
[0027] The reverse proxy unit 130 has a global IP address that is published on the Internet 20. The reverse proxy unit 130 has a reverse proxy function for communicating with the on-premise resources 220 of the on-premise site 200 via the connector unit 300. The reverse proxy unit 130 may further have a load balancer function for distributing the load in response to an increase in the capacity of the number of remote access clients to the on-premise site 200.
[0028] The tunnel connection control unit 140 has a server function of generating a WebSocket tunnel 180 between the reverse proxy unit 130 and the connector unit 300. The tunnel connection control unit 140 performs SSH authentication with the connector unit 300, and if the authentication is successful, generates the WebSocket tunnel 180 between the reverse proxy unit 130 and the connector unit 300. The tunnel connection control unit 140 may perform public key authentication using SSH.
[0029] The reverse proxy unit 130 and the connector unit 300 communicate with each other via a WebSocket tunnel 180. The reverse proxy unit 130 and the connector unit 300 may perform encrypted communication. For example, the reverse proxy unit 130 and the connector unit 300 perform encrypted communication using SSH.
[0030] The service unit 100 may include, for each of a plurality of companies, a license management unit 110, a client support unit 120, a reverse proxy unit 130, and a tunnel connection control unit 140. For example, the service unit 100 realizes the license management unit 110, the client support unit 120, the reverse proxy unit 130, and the tunnel connection control unit 140 as instances for each of a plurality of companies.
[0031] The connector unit 300 has a client function that communicates with the reverse proxy unit 130 and generates a WebSocket tunnel 180. The connector unit 300 uses only outbound connections and does not need to open any ports for inbound connections, so it does not require a fixed global IP address and can eliminate external attacks. The connector unit 300 may have an SSH client function for performing SSH public key authentication using the tunnel connection control unit 140. The connector unit 300 may have a local bridge function and a port mapping function for connections from the client support unit 120.
[0032] The communication terminal 400 may use a secure browser as the browser 410. In other words, the browser 410 may be a secure browser. Note that the browser 410 may also be a general-purpose internet browser.
[0033] As described above, according to the communication system 10 of this embodiment, when the WebSocket tunnel 180 is established, public key authentication using SSH is performed between the service unit 100 and the connector unit 300 installed at the on-premises site 200. This makes it possible to prevent unauthorized connections by third parties. Furthermore, according to the communication system 10, communication data communicated via the WebSocket tunnel 180 may be encrypted using SSH or the like. This makes it possible to make WebSocket tunneling more secure.
[0034] Furthermore, the communication system 10 eliminates the need for a company to disclose the global IP address of the on-premise site 200, thereby reducing the risk of third-party attacks. Furthermore, access from outside the company can be connected via the secure browser of the communication terminal 400 via the service of the service unit 100, and security can be improved by preventing direct connection to the internal company network.
[0035] 2 is an explanatory diagram illustrating processing in the communication system 10. Here, a directory server 222, a file server 224, and a web server 226 are given as examples of on-premise resources 220.
[0036] The connector unit 300 located in the on-premise site 200 sends a connection request to the reverse proxy unit 130. The connector unit 300 may send the connection request to the reverse proxy unit 130 via HTTPS. The connection request may include license information of the company or the like of the on-premise site 200 where the connector unit 300 is located. The reverse proxy unit 130 relays the connection request to the tunnel connection control unit 140.
[0037] Tunnel connection control unit 140 determines whether the license is valid or not based on the contract status managed by license management unit 110. If the connection request is from connector unit 300 of a formally registered company, the license is determined to be valid. If the license information is forged or if a contract was made in the past but has now expired, the license is determined to be invalid.
[0038] If tunnel connection control unit 140 determines that the license is valid, it performs SSH authentication with connector unit 300. One of tunnel connection control unit 140 and connector unit 300 stores a private key, and the other stores a public key corresponding to the private key, and performs SSH authentication using the private key and public key. If SSH authentication is successful, tunnel connection control unit 140 generates WebSocket tunnel 180 between reverse proxy unit 130 and connector unit 300. Even if license authentication determines that the license is valid despite it being invalid, the SSH authentication will fail, preventing unauthorized use.
[0039] The reverse proxy unit 130 and the connector unit 300 may perform encrypted communication when communicating via the WebSocket tunnel 180. In other words, the reverse proxy unit 130 and the connector unit 300 may encrypt and communicate data when communicating data via the WebSocket tunnel 180. The reverse proxy unit 130 and the connector unit 300 may use SSH encrypted communication as the encryption method, or may use another encrypted communication method.
[0040] By generating the WebSocket tunnel 180, preparations are complete to provide a service to the communication terminal 400. The communication terminal 400 transmits a login request to the reverse proxy unit 130 via the Internet 20. The communication terminal 400 may transmit the login request to the reverse proxy unit 130 by HTTPS. The reverse proxy unit 130 relays the login request to the client support unit 120.
[0041] The client support unit 120 may determine whether or not the user 40 can use the service by authenticating the user 40 or the communication terminal 400 using pre-registered authentication information of the user 40. If the client support unit 120 determines that the user 40 cannot use the service, it transmits a message to that effect to the communication terminal 400 via the reverse proxy unit 130.
[0042] If the client handling unit 120 determines that the site is available, it requests the communication terminal 400, via the reverse proxy unit 130, for login information for the on-premise site 200 of the user 40. In response to the request, the communication terminal 400 transmits the login information to the reverse proxy unit 130. The reverse proxy unit 130 relays the received login information to the client handling unit 120.
[0043] The client support unit 120 transmits the received login information to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180. At this time, the reverse proxy unit 130 may transmit the login information to the connector unit 300 via the WebSocket tunnel 180 using encrypted communication. The connector unit 300 relays the received login information to the directory server 222 of the on-premises site 200.
[0044] The directory server 222 authenticates the user 40 based on the received login information and transmits the authentication result to the connector unit 300. The connector unit 300 transmits the received authentication result to the reverse proxy unit 130 via the WebSocket tunnel 180. At this time, the connector unit 300 may transmit the authentication result to the reverse proxy unit 130 via the WebSocket tunnel 180 using encrypted communication. The reverse proxy unit 130 relays the received authentication result to the client support unit 120.
[0045] The client support unit 120 transmits the received authentication result to the communication terminal 400 via the reverse proxy unit 130. If the authentication is successful, the communication terminal 400 becomes able to access resources in the on-premise site 200.
[0046] For example, in accordance with an instruction from the user 40, the communication terminal 400 sends a connection request for the web server 226 of the on-premises site 200 to the reverse proxy unit 130. The reverse proxy unit 130 relays the received connection request to the client association unit 120. In response to receiving the connection request, the client association unit 120 connects to the web server 226 via the reverse proxy unit 130, the WebSocket tunnel 180, and the connector unit 300. The client association unit 120 receives resource information from the web server 226 via the connector unit 300, the WebSocket tunnel 180, and the reverse proxy unit 130. The client association unit 120 may convert the received resource information into HTML data and place it on the web server of the client association unit 120. Furthermore, when the received resource information includes HTML data, the client correspondence unit 120 may convert the on-premise URL described in the HTML data in the resource information into a URL accessible from the communication terminal 400 on the Internet and place the URL on the web server of the client correspondence unit 120. The HTML data may be, for example, data indicating connection to the web server 226 and may include a so-called top page. The HTML data may also be other data. The client correspondence unit 120 converts the internal URL address in the HTML data into a URL address of the web server of the client correspondence unit 120 that the communication terminal 400 can access via the Internet 20. The communication terminal 400 receives the HTML data from the web server of the client correspondence unit 120 via the Internet 20.
[0047] For example, in accordance with an instruction from the user 40, the communication terminal 400 sends a list data request to the reverse proxy unit 130, requesting list data of files stored in the file server 224 of the on-premises site 200. The reverse proxy unit 130 relays the received list data request to the client correspondence unit 120. In response to receiving the list data request, the client correspondence unit 120 connects to the file server 224 via the reverse proxy unit 130, the WebSocket tunnel 180, and the connector unit 300. The client correspondence unit 120 receives the list data from the file server 224 via the connector unit 300, the WebSocket tunnel 180, and the reverse proxy unit 130. The client correspondence unit 120 converts the list data into HTML format. The client correspondence unit 120 places the converted list data on the web server of the client correspondence unit 120. The communication terminal 400 receives the list data from the web server of the client correspondence unit 120 via the Internet 20.
[0048] For example, in accordance with an instruction from the user 40, the communication terminal 400 sends a file request requesting one of the files in the list data to the reverse proxy unit 130. The reverse proxy unit 130 relays the received file request to the client correspondence unit 120. In response to receiving the file request, the client correspondence unit 120 connects to the file server 224 via the reverse proxy unit 130, the WebSocket tunnel 180, and the connector unit 300. The client correspondence unit 120 receives a copy of the target file from the file server 224 via the connector unit 300, the WebSocket tunnel 180, and the reverse proxy unit 130. The communication terminal 400 accesses the file stored in the client correspondence unit 120 via the Internet 20. When the file is edited on the communication terminal 400, the client correspondence unit 120 may notify the file server 224 of the edited content or send a file reflecting the edited content to the file server 224.
[0049] 3 is a diagram illustrating an example of a processing flow in the communication system 10. In the description of FIG. 3, it is assumed that both the connector unit 300 and the user 40 are legitimate.
[0050] In step (sometimes abbreviated as S) 102, the connector unit 300 transmits a connection request to the reverse proxy unit 130. The reverse proxy unit 130 relays the received connection request to the tunnel connection control unit 140.
[0051] In S104, tunnel connection control unit 140 executes license authentication for connector unit 300 based on the contract status managed by license management unit 110. In this example, since connector unit 300 is legitimate, authentication is successful.
[0052] In S106, the tunnel connection control unit 140 performs SSH authentication with the connector unit 300. In this example, the authentication is successful because the connector unit 300 is legitimate. In S108, the tunnel connection control unit 140 creates a WebSocket tunnel 180 between the reverse proxy unit 130 and the connector unit 300.
[0053] In S110, the communication terminal 400 transmits a login request to the reverse proxy unit 130. The reverse proxy unit 130 relays the received login request to the client handling unit 120.
[0054] In S112, the client handling unit 120 executes user authentication of the user 40 of the communication terminal 400. In this example, the user 40 is valid, so the authentication is successful.
[0055] In S114, the client handling unit 120 requests the communication terminal 400 for login information for the user 40 to the on-premise site 200. In S116, the communication terminal 400 transmits the login information to the reverse proxy unit 130 in response to the request. The reverse proxy unit 130 relays the received login information to the client handling unit 120. In S118, the client handling unit 120 transmits the login information to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180.
[0056] In S120, the connector unit 300 executes authentication processing for the received login information. In this example, the user 40 is valid, so authentication is successful. The connector unit 300 transmits the login information to the directory server 222 and receives the authentication result from the directory server 222.
[0057] In S122, the connector unit 300 transmits the authentication result to the reverse proxy unit 130 via the WebSocket tunnel 180. The reverse proxy unit 130 relays the received authentication result to the client handling unit 120. In S124, the client handling unit 120 transmits the authentication result to the communication terminal 400.
[0058] In S126, the communication terminal 400 transmits a connection request to the web server 226 of the on-premise site 200 to the reverse proxy unit 130. The reverse proxy unit 130 relays the connection request to the client handling unit 120.
[0059] In S128, the client handling unit 120 sends a connection request to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180. The connector unit 300 relays the connection request to the web server 226. In S130, the connector unit 300 receives HTML data from the web server 226 and sends it to the reverse proxy unit 130 via the WebSocket tunnel 180. The reverse proxy unit 130 relays the HTML data to the client handling unit 120.
[0060] In S132, the client correspondence unit 120 converts the internal URL address in the HTML data into a URL address of the web server of the client correspondence unit 120 that can be accessed by the communication terminal 400 via the Internet 20. The client correspondence unit 120 places the converted HTML data on the web server of the client correspondence unit 120. In S184, the communication terminal 400 receives the HTML data from the web server of the client correspondence unit 120.
[0061] 4 is an explanatory diagram for explaining the processing in the communication system 10. Here, the processing in the communication system 10 will be described in a case where the connector unit 300 has a private key storage unit 312 that stores a private key, the tunnel connection control unit 140 has a public key storage unit 142 that stores a public key corresponding to the private key, and the communication terminal 400 has a terminal key storage unit 420 that stores a public key corresponding to the private key. The following mainly describes the differences from FIG. 2.
[0062] The connector unit 300 sends a connection request to the reverse proxy unit 130. The reverse proxy unit 130 relays the connection request to the tunnel connection control unit 140. The tunnel connection control unit 140 determines whether the license is valid based on the contract status managed by the license management unit 110. If the tunnel connection control unit 140 determines that the license is valid, it performs SSH authentication with the connector unit 300. The tunnel connection control unit 140 and the connector unit 300 perform SSH authentication using the public key stored in the public key storage unit 142 and the private key stored in the private key storage unit 312. If the SSH authentication is successful, the tunnel connection control unit 140 generates a WebSocket tunnel 180 between the reverse proxy unit 130 and the connector unit 300.
[0063] The communication terminal 400 sends a login request to the reverse proxy unit 130. The reverse proxy unit 130 relays the login request to the client support unit 120. The client support unit 120 may determine whether the user 40 can use the service by authenticating the user 40 or the communication terminal 400 using pre-registered authentication information of the user 40.
[0064] If the client correspondence unit 120 determines that the public key is available, it requests the public key from the communication terminal 400 via the reverse proxy unit 130. In response to the request, the communication terminal 400 transmits the public key stored in the terminal key storage unit 420 to the reverse proxy unit 130. The reverse proxy unit 130 relays the public key to the client correspondence unit 120.
[0065] The client correspondence unit 120 transmits the authentication request, including the received public key, to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180. The connector unit 300 performs SSH authentication using the private key stored in the private key storage unit 312 and the public key included in the received authentication request. The connector unit 300 transmits the authentication result of the SSH authentication to the reverse proxy unit 130 via the WebSocket tunnel 180. The reverse proxy unit 130 relays the received authentication result to the client correspondence unit 120.
[0066] If the authentication result is unsuccessful, the client association unit 120 notifies the communication terminal 400 of the authentication failure via the reverse proxy unit 130. If the authentication result is successful, the client association unit 120 requests login information for the user 40 for the on-premises site 200 from the communication terminal 400 via the reverse proxy unit 130. In response to the request, the communication terminal 400 transmits the login information to the reverse proxy unit 130. The reverse proxy unit 130 relays the received login information to the client association unit 120. The client association unit 120 transmits the login information to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180. The connector unit 300 relays the received login information to the directory server 222 of the on-premises site 200.
[0067] The directory server 222 authenticates the user 40 based on the received login information and transmits the authentication result to the connector unit 300. The connector unit 300 transmits the received authentication result to the reverse proxy unit 130 via the WebSocket tunnel 180. The reverse proxy unit 130 relays the received authentication result to the client support unit 120.
[0068] The client support unit 120 transmits the authentication result to the communication terminal 400. If the authentication is successful, the communication terminal 400 becomes able to access resources at the on-premise site 200.
[0069] Fig. 5 shows an example of a processing flow in the communication system 10. Here, we will explain the flow from when the connector unit 300 sends a connection request to the service unit 100 to when authentication of the user 40 by the directory server 222 is completed in the communication system 10 shown in Fig. 4. We will mainly explain the differences from Fig. 3.
[0070] In S202, the connector unit 300 transmits a connection request to the reverse proxy unit 130. The reverse proxy unit 130 relays the received connection request to the tunnel connection control unit 140.
[0071] In S204, tunnel connection control unit 140 executes license authentication for connector unit 300 based on the contract status managed by license management unit 110. In this example, connector unit 300 is legitimate, so authentication is successful.
[0072] In S206, the tunnel connection control unit 140 performs SSH authentication with the connector unit 300. The tunnel connection control unit 140 and the connector unit 300 perform SSH authentication using the public key stored in the public key storage unit 142 and the private key stored in the private key storage unit 312. In this example, the connector unit 300 is valid, so the authentication is successful. In S208, the tunnel connection control unit 140 generates a WebSocket tunnel 180 between the reverse proxy unit 130 and the connector unit 300.
[0073] In S210, the communication terminal 400 transmits a login request to the reverse proxy unit 130. The reverse proxy unit 130 relays the received login request to the client handling unit 120.
[0074] In S212, the client support unit 120 executes user authentication of the user 40 of the communication terminal 400. In this example, the user 40 is valid, so the authentication is successful.
[0075] In S214, the client handling unit 120 requests the public key from the communication terminal 400 via the reverse proxy unit 130. In S216, in response to the request, the communication terminal 400 transmits the public key stored in the terminal key storage unit 420 to the reverse proxy unit 130. The reverse proxy unit 130 relays the public key to the client handling unit 120.
[0076] In S218, the client correspondence unit 120 sends an authentication request including the received public key to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180. In S220, the connector unit 300 performs SSH authentication using the private key stored in the private key storage unit 312 and the public key included in the received authentication request. In this example, the user 40 is valid, so authentication is successful. In S222, the connector unit 300 sends the authentication result of the SSH authentication to the reverse proxy unit 130 via the WebSocket tunnel 180. The reverse proxy unit 130 relays the received authentication result to the client correspondence unit 120.
[0077] In S224, the client handling unit 120 requests login information for the user 40 to the on-premise site 200 from the communication terminal 400 via the reverse proxy unit 130. In S226, the communication terminal 400 transmits the login information to the reverse proxy unit 130 in response to the request. The reverse proxy unit 130 relays the received login information to the client handling unit 120. In S228, the client handling unit 120 transmits the login information to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180.
[0078] In S230, the connector unit 300 executes authentication processing for the received login information. The connector unit 300 transmits the login information to the directory server 222 and receives the authentication result from the directory server 222.
[0079] In S232, the connector unit 300 transmits the authentication result to the reverse proxy unit 130 via the WebSocket tunnel 180. The reverse proxy unit 130 relays the received authentication result to the client handling unit 120. In S234, the client handling unit 120 transmits the authentication result to the communication terminal 400.
[0080] 6 is an explanatory diagram for explaining the processing in the communication system 10. Here, the processing in the communication system 10 will be described in a case where the tunnel connection control unit 140 has a private key storage unit 144 that stores a private key, the connector unit 300 has a public key storage unit 314 that stores a public key corresponding to the private key, and the communication terminal 400 has a terminal key storage unit 420 that stores a public key corresponding to the private key. The following mainly describes the points that are different from FIG. 4.
[0081] The connector unit 300 sends a connection request to the reverse proxy unit 130. The reverse proxy unit 130 relays the connection request to the tunnel connection control unit 140. The tunnel connection control unit 140 determines whether the license is valid based on the contract status managed by the license management unit 110. If the tunnel connection control unit 140 determines that the license is valid, it performs SSH authentication with the connector unit 300. The tunnel connection control unit 140 and the connector unit 300 perform SSH authentication using the private key stored in the private key storage unit 144 and the public key stored in the public key storage unit 314. If the SSH authentication is successful, the tunnel connection control unit 140 generates a WebSocket tunnel 180 between the reverse proxy unit 130 and the connector unit 300.
[0082] The communication terminal 400 sends a login request to the reverse proxy unit 130. The reverse proxy unit 130 relays the login request to the client support unit 120. The client support unit 120 may determine whether the user 40 can use the service by authenticating the user 40 or the communication terminal 400 using pre-registered authentication information of the user 40.
[0083] If the client correspondence unit 120 determines that the public key is available, it requests the public key from the communication terminal 400 via the reverse proxy unit 130. In response to the request, the communication terminal 400 transmits the public key stored in the terminal key storage unit 420 to the reverse proxy unit 130. The reverse proxy unit 130 relays the public key to the client correspondence unit 120.
[0084] The client association unit 120 performs SSH authentication using the received public key and the private key stored in the private key storage unit 144. If the authentication result is unsuccessful, the client association unit 120 notifies the communication terminal 400 of the authentication failure via the reverse proxy unit 130. If the authentication is successful, the client association unit 120 requests login information for the user 40 for the on-premises site 200 from the communication terminal 400 via the reverse proxy unit 130. In response to the request, the communication terminal 400 transmits the login information to the reverse proxy unit 130. The reverse proxy unit 130 relays the received login information to the client association unit 120. The client association unit 120 transmits the login information to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180. The connector unit 300 relays the received login information to the directory server 222 of the on-premises site 200.
[0085] The directory server 222 authenticates the user 40 using the received login information and sends the authentication result to the connector unit 300. The connector unit 300 sends the received authentication result to the reverse proxy unit 130 via the WebSocket tunnel 180. The reverse proxy unit 130 relays the received authentication result to the client support unit 120. The client support unit 120 sends the authentication result to the communication terminal 400. If the authentication is successful, the communication terminal 400 is able to access resources at the on-premises site 200.
[0086] Fig. 7 shows an example of a processing flow in the communication system 10. Here, we will explain the flow from when the connector unit 300 sends a connection request to the service unit 100 to when authentication of the user 40 by the directory server 222 is completed in the communication system 10 shown in Fig. 6. We will mainly explain the differences from Fig. 5.
[0087] In S302, the connector unit 300 transmits a connection request to the reverse proxy unit 130. The reverse proxy unit 130 relays the received connection request to the tunnel connection control unit 140.
[0088] In S304, tunnel connection control unit 140 executes license authentication for connector unit 300 based on the contract status managed by license management unit 110. In this example, since connector unit 300 is legitimate, authentication is successful.
[0089] In S306, the tunnel connection control unit 140 performs SSH authentication with the connector unit 300. The tunnel connection control unit 140 and the connector unit 300 perform SSH authentication using the public key stored in the public key storage unit 314 and the private key stored in the private key storage unit 144. In this example, the connector unit 300 is legitimate, so the authentication is successful. In S308, the tunnel connection control unit 140 generates a WebSocket tunnel 180 between the reverse proxy unit 130 and the connector unit 300.
[0090] In S310, the communication terminal 400 transmits a login request to the reverse proxy unit 130. The reverse proxy unit 130 relays the received login request to the client handling unit 120.
[0091] In S312, the client handling unit 120 executes user authentication of the user 40 of the communication terminal 400. In this example, the user 40 is valid, so the authentication is successful.
[0092] In S314, the client handling unit 120 requests the public key from the communication terminal 400 via the reverse proxy unit 130. In S316, in response to the request, the communication terminal 400 transmits the public key stored in the terminal key storage unit 420 to the reverse proxy unit 130. The reverse proxy unit 130 relays the public key to the client handling unit 120.
[0093] In S318, the client interface unit 120 performs SSH authentication using the received public key and the private key stored in the private key storage unit 144. In this example, the user 40 is legitimate, so the authentication is successful.
[0094] In S320, the client handling unit 120 requests login information for the user 40 to the on-premise site 200 from the communication terminal 400 via the reverse proxy unit 130. In S322, the communication terminal 400 transmits the login information to the reverse proxy unit 130 in response to the request. The reverse proxy unit 130 relays the received login information to the client handling unit 120. In S324, the client handling unit 120 transmits the login information to the connector unit 300 via the reverse proxy unit 130 and the WebSocket tunnel 180.
[0095] In S326, the connector unit 300 executes authentication processing for the received login information. The connector unit 300 transmits the login information to the directory server 222 and receives an authentication result from the directory server 222. In S328, the connector unit 300 transmits the authentication result to the reverse proxy unit 130 via the WebSocket tunnel 180. The reverse proxy unit 130 relays the received authentication result to the client support unit 120. In S330, the client support unit 120 transmits the authentication result to the communication terminal 400.
[0096] 8 schematically shows an example of the hardware configuration of a computer 1200 that functions as the service unit 100 or the connector unit 300. A program installed on the computer 1200 can cause the computer 1200 to function as one or more "units" of an apparatus according to the present embodiment, or can cause the computer 1200 to execute operations associated with the apparatus according to the present embodiment or one or more "units," and / or can cause the computer 1200 to execute a process according to the present embodiment or steps of the process. Such a program can be executed by the CPU 1212 to cause the computer 1200 to perform specific operations associated with some or all of the blocks in the flowcharts and block diagrams described herein.
[0097] The computer 1200 according to this embodiment includes a CPU 1212, a RAM 1214, and a graphics controller 1216, which are interconnected by a host controller 1210. The computer 1200 also includes input / output units such as a communications interface 1222, a storage device 1224, a DVD drive 1226, and an IC card drive, which are connected to the host controller 1210 via an input / output controller 1220. The DVD drive 1226 may be a DVD-ROM drive, a DVD-RAM drive, or the like. The storage device 1224 may be a hard disk drive, a solid-state drive, or the like. The computer 1200 also includes a ROM 1230 and legacy input / output units such as a keyboard, which are connected to the input / output controller 1220 via an input / output chip 1240.
[0098] The CPU 1212 operates according to programs stored in the ROM 1230 and the RAM 1214, thereby controlling each unit. The graphics controller 1216 acquires image data generated by the CPU 1212 into a frame buffer or the like provided in the RAM 1214 or into the graphics controller 1216 itself, and causes the image data to be displayed on the display device 1218.
[0099] The communication interface 1222 communicates with other electronic devices via a network. The storage device 1224 stores programs and data used by the CPU 1212 in the computer 1200. The DVD drive 1226 reads programs or data from a DVD-ROM 1227 or the like and provides them to the storage device 1224. The IC card drive reads programs and data from an IC card and / or writes programs and data to an IC card.
[0100] The ROM 1230 stores therein a boot program or the like that is executed by the computer 1200 upon activation, and / or programs that depend on the hardware of the computer 1200. The input / output chip 1240 may also connect various input / output units to the input / output controller 1220 via a USB port, a parallel port, a serial port, a keyboard port, a mouse port, etc.
[0101] The programs are provided by a computer-readable storage medium such as a DVD-ROM 1227 or an IC card. The programs are read from the computer-readable storage medium, installed in the storage device 1224, RAM 1214, or ROM 1230, which are also examples of computer-readable storage media, and executed by the CPU 1212. Information processing described in these programs is read by the computer 1200, and brings about cooperation between the programs and the various types of hardware resources described above. An apparatus or a method may be configured by implementing operations or processing of information in accordance with the use of the computer 1200.
[0102] For example, when communication is performed between computer 1200 and an external device, CPU 1212 may execute a communication program loaded into RAM 1214 and instruct communication interface 1222 to perform communication processing based on the processing described in the communication program. Under the control of CPU 1212, communication interface 1222 reads transmission data stored in a transmission buffer area provided in RAM 1214, storage device 1224, DVD-ROM 1227, or a recording medium such as an IC card, and transmits the read transmission data to a network, or writes received data received from the network to a reception buffer area or the like provided on the recording medium.
[0103] Furthermore, the CPU 1212 may cause all or a necessary portion of a file or database stored in an external recording medium such as the storage device 1224, the DVD drive 1226 (DVD-ROM 1227), an IC card, etc. to be read into the RAM 1214, and may perform various types of processing on the data on the RAM 1214. The CPU 1212 may then write back the processed data to the external recording medium.
[0104] Various types of information, such as various types of programs, data, tables, and databases, may be stored on the recording medium and may undergo information processing. The CPU 1212 may perform various types of processing on data read from the RAM 1214, including various types of operations, information processing, conditional judgment, conditional branching, unconditional branching, information search / replacement, etc., as described throughout this disclosure and specified by the instruction sequences of the programs, and write the results back to the RAM 1214. The CPU 1212 may also search for information in a file, database, etc. on the recording medium. For example, if multiple entries, each having an attribute value of a first attribute associated with an attribute value of a second attribute, are stored on the recording medium, the CPU 1212 may search for an entry whose attribute value of the first attribute matches a specified condition from among the multiple entries, read the attribute value of the second attribute stored in the entry, and thereby obtain the attribute value of the second attribute associated with the first attribute that satisfies a predetermined condition.
[0105] The above-described programs or software modules may be stored in a computer-readable storage medium on or near the computer 1200. A recording medium such as a hard disk or RAM provided in a server system connected to a dedicated communication network or the Internet can also be used as a computer-readable storage medium, thereby providing the programs to the computer 1200 via the network.
[0106] The blocks in the flowcharts and block diagrams in the present embodiments may represent stages of a process in which an operation is performed or "parts" of a device responsible for performing the operation. Particular stages and "parts" may be implemented by dedicated circuitry, programmable circuitry provided with computer-readable instructions stored on a computer-readable storage medium, and / or a processor provided with computer-readable instructions stored on a computer-readable storage medium. The dedicated circuitry may include digital and / or analog hardware circuits, including integrated circuits (ICs) and / or discrete circuits. The programmable circuitry may include reconfigurable hardware circuits, such as field programmable gate arrays (FPGAs) and programmable logic arrays (PLAs), including AND, OR, XOR, NAND, NOR, and other logical operations, flip-flops, registers, and memory elements.
[0107] A computer-readable storage medium may include any tangible device capable of storing instructions that are executed by an appropriate device, such that a computer-readable storage medium having instructions stored thereon comprises an article of manufacture, including instructions that can be executed to create means for performing the operations specified in the flowcharts or block diagrams. Examples of computer-readable storage media may include electronic, magnetic, optical, electromagnetic, and semiconductor storage media. More specific examples of computer-readable storage media may include floppy disks, diskettes, hard disks, random access memories (RAMs), read-only memories (ROMs), erasable programmable read-only memories (EPROMs or flash memories), electrically erasable programmable read-only memories (EEPROMs), static random access memories (SRAMs), compact disc read-only memories (CD-ROMs), digital versatile discs (DVDs), Blu-ray discs, memory sticks, integrated circuit cards, and the like.
[0108] The computer readable instructions may include either assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, or source or object code written in any combination of one or more programming languages, including object-oriented programming languages such as Smalltalk®, JAVA®, C++, etc., and conventional procedural programming languages such as the “C” programming language or similar programming languages.
[0109] Computer-readable instructions may be provided locally or over a local area network (LAN), a wide area network (WAN) such as the Internet, to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, or programmable circuitry, such that the processor or programmable circuitry executes the computer-readable instructions to generate means for performing the operations specified in the flowcharts or block diagrams. Examples of processors include computer processors, processing units, microprocessors, digital signal processors, controllers, microcontrollers, etc.
[0110] Although the present invention has been described above using embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various modifications and improvements can be made to the above embodiments. It is clear from the claims that such modifications and improvements can also be included within the technical scope of the present invention.
[0111] It should be noted that the order of execution of each process, such as operations, procedures, steps, and stages, in the devices, systems, programs, and methods shown in the claims, specifications, and drawings is not specifically stated as "before," "prior to," etc., and that the processes can be performed in any order unless the output of a previous process is used in a subsequent process. Even if the operational flow in the claims, specifications, and drawings is described using "first," "next," etc. for convenience, this does not mean that the processes must be performed in this order.
[0112] 10 Communication system, 20 Internet, 100 Service unit, 110 License management unit, 120 Client support unit, 130 Reverse proxy unit, 140 Tunnel connection control unit, 142 Public key storage unit, 144 Private key storage unit, 180 WebSocket tunnel, 200 On-premise site, 210 Firewall, 220 On-premise resource, 222 Directory server, 224 File server, 226 Web server, 300 Connector unit, 312 Private key storage unit, 314 Public key storage unit, 400 Communication terminal, 410 Browser, 420 Terminal key storage unit, 1200 Computer, 1210 Host controller, 1212 CPU, 1214 RAM, 1216 Graphics controller, 1218 Display device, 1220 Input / output controller, 1222 Communication interface, 1224 Storage device, 1226 DVD drive, 1227 DVD-ROM, 1230 ROM, 1240 I / O chip
Claims
1. A communication system comprising: a connector unit located within an on-premise site; and a service unit, wherein the service unit has: a reverse proxy unit that communicates with the connector unit and a communication terminal via the Internet; a tunnel connection control unit that performs SSH authentication with the connector unit and, if the authentication is successful, generates a WebSocket tunnel between the reverse proxy unit and the connector unit; and a client support unit that receives resource information within the on-premise site that corresponds to the connector unit via the WebSocket tunnel by encrypted communication, and transmits the resource information to the communication terminal via the reverse proxy unit.
2. The communication system according to claim 1, wherein the client support unit executes the encrypted communication using SSH.
3. The communication system described in claim 2, wherein the tunnel connection control unit performs the SSH authentication between the reverse proxy unit and the connector unit when the reverse proxy unit receives a connection request from the connector unit, and generates the WebSocket tunnel between the reverse proxy unit and the connector unit if the authentication is successful.
4. The communication system described in claim 3, wherein when the reverse proxy unit receives a login request from the communication terminal to the service unit by a user of the communication terminal, the client support unit authenticates the user, and if the authentication is successful, receives login information for the user for the on-premises site from the communication terminal and transmits the login information to a directory server of the on-premises site via the WebSocket tunnel.
5. The communication system described in claim 4, wherein when the client corresponding unit receives a request to the web server of the on-premises site from the communication terminal of the user whose login information has been successfully authenticated by the directory server, the client corresponding unit accesses the web server of the on-premises site via the WebSocket tunnel to receive the resource information, converts the resource information into HTML data, and places it on the web server of the client corresponding unit.
6. The communication system described in claim 4, wherein when the client corresponding unit receives a request to the web server of the on-premises site from the communication terminal of the user whose login information has been successfully authenticated by the directory server, the client corresponding unit accesses the web server of the on-premises site via the WebSocket tunnel to receive the resource information, converts the on-premises URL described in the HTML data in the resource information into a URL accessible from the communication terminal on the Internet, and places the URL on the web server of the client corresponding unit.
7. A communications system as claimed in any one of claims 1 to 6, wherein the connector unit has a private key memory unit that stores a private key for SSH authentication, the tunnel connection control unit has a public key memory unit that stores a public key corresponding to the private key, and the tunnel connection control unit and the connector unit perform the SSH authentication using the private key and the public key.
8. The communication system described in claim 7, wherein the communication terminal has a terminal key memory unit that stores a public key corresponding to the private key, and when the client corresponding unit receives an SSH authentication request including the public key stored in the terminal key memory unit from the communication terminal via the reverse proxy unit, the client corresponding unit sends the SSH authentication request to the connector unit via the WebSocket tunnel, and the connector unit performs SSH authentication for the received SSH authentication request using the public key included in the SSH authentication request and the private key stored in the private key memory unit, and if the authentication is successful, sends success notification data to the client corresponding unit notifying that the authentication has been successful, and in response to receiving the success notification data, the client corresponding unit requests login information for the on-premises site of the user of the communication terminal from the communication terminal.
9. A communications system according to any one of claims 1 to 6, wherein the tunnel connection control unit has a private key memory unit that stores a private key for SSH authentication, the connector unit has a public key memory unit that stores a public key corresponding to the private key, and the tunnel connection control unit and the connector unit perform the SSH authentication using the private key and the public key.
10. The communication system of claim 9, wherein the communication terminal has a terminal key memory unit that stores a public key corresponding to the private key, and when the client support unit receives an SSH authentication request including the public key stored in the terminal key memory unit from the communication terminal via the reverse proxy unit, the client support unit performs SSH authentication using the public key included in the SSH authentication request and the private key stored in the private key memory unit, and if the authentication is successful, requests login information for the on-premises site of the user of the communication terminal from the communication terminal.
11. An information processing device comprising: a reverse proxy unit that communicates with a communication terminal and a connector unit located within an on-premises site via the Internet; a tunnel connection control unit that performs SSH authentication with the connector unit and, if authentication is successful, generates a WebSocket tunnel between the reverse proxy unit and the connector unit; and a client support unit that receives resource information within the on-premises site corresponding to the connector unit via the WebSocket tunnel using encrypted communication, and transmits the resource information to the communication terminal via the reverse proxy unit.
12. A program for causing a computer to function as the information processing device according to claim 11.
13. An information processing method executed by a computer, comprising: a tunnel connection control step of performing SSH authentication with a connector unit located within an on-premises site via the Internet, and generating a WebSocket tunnel with the connector unit if the authentication is successful; a receiving step of receiving resource information within the on-premises site corresponding to the connector unit by encrypted communication via the WebSocket tunnel; and a transmitting step of transmitting the resource information to a communication terminal via the Internet.
14. A connector device comprising: a private key memory unit that stores a private key for SSH authentication; and a connector unit that performs SSH authentication using the private key with a service unit located in a cloud via the Internet, and generates a WebSocket tunnel with the service unit if the authentication is successful.
Citation Information
Patent Citations
Remote work information protection system
JP2022081071A
Method for implementing extensible trusted SSH
CN101888383A
Container cluster system, container console and server
CN113364727A
Intranet equipment connection method and system based on SSH reverse tunnel
CN113872957A
A remote access system using the SSH protocol and managing SSH authentication key securely
KR101992976B1
