Mappings

Mappings define where an STLink will route traffic to that it receives, and are generally considered the "server" ends of a SealedTunnel connection.

A Mapping consists of an IP address and port, often times the loopback address. In some cases, the Mapping may be a Private IP Address of another machine in the network.

Mappings require that a service listen on the port that the STLink is forwarding traffic to.

Connection data flowing to the destination service can be encrypted beyond the triple-layer encryption provided by Xiid, so long as the service has the ability to decrypt the traffic.

A common scenario where this will occur is with web services that use TLS certificates. The original TLS certificates and headers will be preserved from the original connection after the STLink has decrypted Xiid's triple-layer encryption and forwarded the connection to the service. This makes leveraging DNS Routing paramount, so that the original HTTP/S connection will be preserved and certificate validation will operate normally.

To view the Mappings available on the STLink, you can navigate to the Mappings tab of the STLink Portal. The Mappings tab will provide information on where the STLink is routing incoming connections. The key pieces of information are the Description and Serving resource from (Mapping) columns.

Information	Description
Description	The description of the resource that this Mapping will route to
Mapping	The IP address and port that the STLink will route incoming connections to
IP Address	The IP address that the STLink will route incoming connections to
Port	The port that the STLink will route incoming connections to