This article is intended for customers who are considering implementing HENNGE Connect.
This article describes a flow-diagram of HENNGE Connect and a communication path to an on-premise web system through HENNGE Connect.
Flow-diagram and communication path
Communication path when tunneling is created
Communication between the HENNGE Connect public URL and the on-premises web system is done via the HENNGE Connect agent.
When HENNGE Connect is launched, it creates tunneling and initiates communication between the on-premise web system and the public URL.
The on-premise web system communicates with the HENNGE Connect agent through HTTP (TCP/80) or HTTPS (TCP/443).
The HENNGE Connect agent communicates with the public URL through HTTPS (TCP/443).
Tunneling is a virtual communication path between the HENNGE Connect agent and the public URL that is invisible on the network.
Only outbound communication takes place within tunneling when the HENNGE Connect agent communicates with the public URL.
It realizes secure communication as Inbound communication does not take place when the public URL communicates with the HENNGE Connect agent.
Communication path of first-time user authentication
Unauthenticated users access HENNGE Access Control from their clients for user authentication.
Authentication with HENNGE Accecss Control allows communication with on-premise web systems, via the public URL which is linked with SAML authentication.
Communication path when accessing on-premise web systems after authentication
Authenticated users can also access the on-premise web system directly from their clients via the public URL, through HTTPS (TCP/443).