Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Scroll Documents: Update page title prefix

This article describes the communication flow of a secure terminal session in the IGEL Universal Management Suite (UMS) environment.

...

IGEL OS 12

Direct Connection

Before the secure terminal flow:

...

  1. The UMS Console requests the UMS Server to initiate a secure terminal session.
  2. The UMS Server requests the device via the Unified Protocol WebSocket to open the secure terminal session.
  3. The device opens the WebSocket tunnel for secure terminal data to the UMS Server and starts the secure terminal session.
  4. The UMS Server forwards the secure terminal session information to the UMS Console.
  5. The UMS Console opens the WebSocket tunnel for secure terminal data to the UMS Server and starts the secure terminal session.
  6. The terminal data is sent through the opened WebSockets.

Drawio
diagramNamerevision
bordertrue1
zoom1
simple1
pageId71926982
custContentId74813919
lbox1
diagramDisplayNameTerminal_DirectConnection_OS12simpleViewertrue
contentVer1
revision11
baseUrlhttps://igel-jira.atlassian.net/wiki
diagramNameTerminal_DirectConnection_OS12
width600
linksauto
tbstylehidden
lboxtrue
diagramWidth1003
11

Over ICG

Before the secure terminal flow:

...

  1. The UMS Console requests the UMS Server to initiate a secure terminal session.
  2. The UMS Server requests the ICG to open a secure terminal session.
  3. The ICG requests the device via the Unified Protocol WebSocket to open a secure terminal session and the UMS Server forwards the secure terminal session information to the UMS Console.
  4. The device opens the WebSocket tunnel for secure terminal data to the ICG and starts the secure terminal session and the UMS Console opens the WebSocket tunnel for secure terminal data to the ICG and starts the secure terminal session.
  5. The terminal data is sent through the opened WebSockets.

Drawio
diagramName
bordertrue1
zoom1
simple1
pageId71926982
custContentId74912721
lbox1
diagramDisplayNameTerminal_ICG_OS12simpleViewertrue
contentVer1
revision11
baseUrlhttps://igel-jira.atlassian.net/wiki
diagramNameTerminal_ICG_OS12
width600
linksauto
tbstylehidden
lboxtrue
diagramWidth1441
revision11

IGEL OS 11 or Earlier

Direct Connection

The UMS Console establishes a connection to the UMS Server. The UMS Server then establishes a TLS tunnel to the device. 

The following figure illustrates the communication between the UMS Console, the UMS Server and a device:

Drawio
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameSecure Terminal
simpleViewertrue1
zoom1
simple1
pageId71926982
custContentId74813922
lbox1
diagramDisplayNameSecure Terminal
contentVer1
revision1
baseUrlhttps://igel-jira.atlassian.net/wiki
diagramNameSecure Terminal
width600
linksauto
tbstyletop
lboxtrue
diagramWidth783
revision1

Over ICG

Both the UMS Server and the device have established a WebSocket connection to the ICG; this WebSocket is used for commands from the UMS and messages from the device. 

The UMS Console and the device establish a dedicated WebSocket for the secure terminal with the ICG. 

Drawio
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameSecureTerminalOverICG
simpleViewertrue1
zoom1
simple1
pageId71926982
custContentId74912723
lbox1
diagramDisplayNameSecureTerminalOverICG
contentVer1
revision1
baseUrlhttps://igel-jira.atlassian.net/wiki
diagramNameSecureTerminalOverICG
width600
linksauto
tbstylehidden
lboxtrue
diagramWidth783
revision1