What's new with Boundary Desktop and Boundary 0.1.8
We are pleased to announce the release of HashiCorp Boundary 0.1.8 and the beta release of Boundary Desktop. Boundary Desktop gives users the ability to connect to remote targets, view active session details, all from a convenient macOS desktop application (Windows support planned).
This release of Boundary has a number of improvements and bug fixes, including:
If you have used Boundary before, you may be familiar with its command line interface. Boundary takes an API-first approach to configuring your landscape of infrastructure targets, identities, and access permissions. While this makes it easy for developers and security administrators to automate infrastructure access management, we have heard from administrators that they would also greatly benefit from a UI-driven workflow as well. Boundary Desktop solves this problem, by enabling the following actions:
Here is a short video navigating through the interface:
We consider this release of the desktop client to be stable enough to put into our end-users hands, but we’re still working through ongoing feature development leading up to general availability.
The release is just the beginning of Boundary Desktop. In the coming months you can expect iterative improvements to Boundary Desktop, including:
To get started, head over to the Boundary Desktop guide, where you will learn how to install Boundary Desktop and connect to your first instance.
Learn how to migrate HashiCorp Boundary from one KMS provider to another, and learn more about how its encryption works.
HashiCorp’s Rift proof-of-concept app automatically grants and revokes infrastructure access to on-call engineers when an incident is triggered and resolved.
Here’s how to use HashiCorp Boundary to provide identity-based remote access and credential management for Kubernetes clusters.