»Boundary Desktop

Boundary Desktop is a standalone application that provides a simple interface for browsing and connecting to targets on your local computer (macOS currently supported). Launch a session in Boundary Desktop and then make a connection using your favorite tooling!

»Getting Started

$ boundary dev

»Install Boundary Desktop

  1. Download the latest .dmg installer from our releases page
  2. Double-click the downloaded .dmg to run the installer
  3. Drag and drop Boundary into the applications folder

»Run Boundary Desktop

  1. Open the Boundary Desktop application
  2. You'll be prompted for the Boundary server origin, this is the URL for the client to connect to the Boundary API. If you are running a local dev mode server, this URL will be http://localhost:9200
  3. You can now login to Boundary. We're using a dev mode server in this example with the username admin and the password password
  4. After logging in, you should see the targets your user is authorized to connect to. Since we are using a dev mode server we see the default generated target for 127.0.0.1:22

»Connect!

  1. Click on connect next to the default target. A pop-up window will display the local address of the proxy and the ephemeral port for the session
  2. Navigate to the Sessions pane and you'll see this session is in pending state because we haven't made a connection to it yet (but will!)
  1. On the CLI, ssh to the target using the local ephemeral port created in the previous step
$ ssh -p 49250 127.0.0.1
The authenticity of host '[127.0.0.1]:49250 ([127.0.0.1]:49250)' can't be established.
ECDSA key fingerprint is SHA256:glO05n2iT8Roqak5G63gMKnW8qsE0lxy0MPWcWC7iqg.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[127.0.0.1]:49250' (ECDSA) to the list of known hosts.
Password:
Last login: Thu Feb 11 17:49:09 2021
$ 
  1. Navigate back to the sessions view and you'll see this session is now active
  2. Click Cancel to cancel the session and you'll see the status go to cancelling briefly, then terminated
  3. Navigate back to the CLI and you'll see your SSH session has closed