Skip to content

URI Schemas ​

The secure design of the Xiid platform does not allow Xiid's software to examine any traffic within the SealedTunnel.

As a result, the platform does not have an inherent way to provide assistance to end-users with accessing connections through the SealedTunnel.

The optional Helper Text field available when setting up a Binding Route can be configured to provide this information to the STLinks that have been assigned the route.

If the Helper Text field is filled with a supported URI that describes the protocol used for connecting through the binding route (listed below), the STLink can automatically provide user-friendly access to the resource to users.

Supported URIs ​

Xiid supports the following URIs in the STLink Portal:

HTTP/S

Used for websites, web applications, domain names and ports

Examples:

  • http://127.4.4.4
  • http://127.4.4.4:8000
  • https://example.com
  • https://example.com:8443

RDP

Used for Remote Desktop applications through a downloadable .rdp file

Examples:

  • rdp://12.4.4.4
  • rdp://12.4.4.4:13389
  • rdp://windows.example.com
  • rdp://windows.example.com@user
  • rdp://windows.example.com:13389@user

SSH

Used for opening an SSH connection via the browser (macOS and Linux Only) which in turn launches the Terminal, for downloading an .sh file, or for copying the SSH command to the clipboard

Examples:

  • ssh://127.4.4.4
  • ssh://127.4.4.4:1022
  • ssh://linux.example.com
  • ssh://linux.example.com:1022
  • ssh://linux.example.com:1022@user

S/FTP

Used for S/FTP by copying the URI to the clipboard

Examples:

  • ftp://127.4.4.4
  • ftp://127.4.4.4:1020
  • ftps://com.example
  • ftps://com.example:1020

PostgreSQL/SQL

Used for accessing a database by copying a SQL URI to the clipboard

Examples:

  • postgresql://user@localhost:5432/mydatabase
  • sql://user@localhost:5432/mydatabase

SMB

Used for opening a file browser window to the SMB fileshare, or for copying a link to the shared network directory to the clipboard

Examples:

  • smb://mydomain;myuser@servername/myshare