The latest release of HashiCorp Boundary includes managed groups and OIDC configuration improvements, while Boundary Desktop is now available on Windows.
We are pleased to announce the release of HashiCorp Boundary 0.3 and the Windows release of Boundary Desktop 1.1. Boundary provides identity-based access management for dynamic infrastructure. Boundary 0.3 includes several key features and improvements:
Boundary 0.3.0 includes a new variant of our desktop client that is compatible with Microsoft Windows operating systems. This variant is exactly the same in terms of feature parity with our existing macOS desktop client, and provides our Windows users the same ease-of-use for starting, stopping, and observing sessions from one easy graphical interface.
To download the new Boundary Desktop client for Windows, navigate to our releases page to download our Windows-specific installation. Documentation for installing on Windows has also been added to our documentation site.
In Boundary 0.2.0 we released a new OIDC (OpenID Connect) authentication method. This authentication method allows users to integrate Boundary with existing identity systems such as Microsoft Azure Active Directory, AWS Identity and Access Management (IAM), and popular single sign-on services like Okta and Auth0. Configuration of the OIDC authentication method had been available only via the command line or through our Terraform provider. Boundary 0.3.0 includes the ability to configure OIDC authentication methods through our graphical administrator interface. This provides another option when setting up OIDC authentication methods for users.
Managed groups allow the population of Boundary groups based on external IdP metadata. This feature allows users of our OIDC authentication method to automatically create groups based on the IdP they’re integrating with over OIDC.
We’re working hard on a new Learn guide for the managed groups resource, but in the meantime, you can read about how it fits into our domain model in our docs. Along with the Learn guide, be on the lookout for a new release of our Terraform provider that will include the managed groups resource in the next couple of weeks.
As always, we recommend upgrading and testing this release in an isolated environment. If you experience any issues, please report them on the Boundary GitHub issue tracker or post to the Boundary discussion forum. As a reminder, if you believe you have found a security issue in Boundary, please responsibly disclose it by emailing firstname.lastname@example.org — do not use the public issue tracker. Our security policy and our PGP key can be found on the HashiCorp security page.
We hope you enjoy Boundary 0.3.
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.