Target
This is applicable to customers who can use HENNGE Connect.
(Please check here for a list of features available for each contract license.)
Purpose
This document explains the configuration of HENNGE Connect and the communication route to the on-premises web system when using HENNGE Connect.
Configuration Explanation
Route for Configuring Tunneling
Communication between HENNGE Connect's public URL and the on-premises web system is done through 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 (TCP/80) or https (TCP/443).
The HENNGE Connect agent communicates with the public URL via https (TCP/443).
Note: Tunneling is a virtual communication route invisible on the network that connects the HENNGE Connect agent and the public URL.
Communication within the tunneling is only outbound communication from the HENNGE Connect agent to the public URL.
Inbound communication from the public URL to the HENNGE Connect agent is not performed, ensuring secure communication.
Route for Performing Initial User Authentication
Unauthenticated users access HENNGE Access Control via https (TCP/443) from the client terminal to perform user authentication.
By authenticating with HENNGE Access Control, communication with the on-premises web system linked via SAML authentication integration becomes possible.
Route for Accessing the On-Premises Web System After Authentication
Authenticated users can also directly access the on-premises web system via the public URL using https (TCP/443) from the client terminal.
References
・Overview of HENNGE Connect Features