Include
- Customers using Access Control
- Customers who can use HENNGE Connect
(For a list of features available per license, please check here.)
Purpose
- This article explains the configuration of HENNGE Connect and the communication path to on-premises web systems when using HENNGE Connect.
Notes
- The network configuration to establish communication between the on-premises web system and the HENNGE Connect agent must be configured and verified by the customer.
- The content of this article is based on the product as of October 2025 and may change without notice thereafter.
Description
Path when configuring tunneling
Communication between the public URL of HENNGE Connect and the on-premises web system is conducted via the HENNGE Connect agent.
By starting the HENNGE Connect agent, tunneling is configured, and communication between the on-premises web system and the public URL begins.
The on-premises web system communicates with the HENNGE Connect agent via http or https.
The HENNGE Connect agent communicates with the public URL via https (TCP/443).
Note: Tunneling is a virtual communication path that is invisible on the network, connecting the HENNGE Connect agent and the public URL.
Communication within the tunnel is only outbound from the HENNGE Connect agent to the public URL.
Inbound communication from the public URL to the HENNGE Connect agent does not occur, ensuring secure communication.
Path when performing initial user authentication
Unauthenticated users access Access Control from the client terminal via https (TCP/443) to perform user authentication.
By authenticating with Access Control, communication with the on-premises web system via the authenticated public URL becomes possible.
Path when accessing the on-premises web system after authentication
Authenticated users can also access the on-premises web system directly from the client terminal via https (TCP/443) through the public URL.
Reference
・HENNGE Connect Feature Overview