Next Steps
For Boundary's upcoming releases, we have 3 key product themes we’re focused on delivering:
Bring your own identity. We feel strongly that Boundary’s identity-based controls should use the same identity that users have for their other applications. To do so, we’ll progressively add support for new auth methods for Boundary. Our first step will be in delivering an OpenID Connect (OIDC) auth method.
Just-in-time access. A just-in-time access posture will be enforced at multiple levels within Boundary. Upcoming releases will offer integration with
Vault or your preferred secret management solution of choice to generate ephemeral credentials for Boundary sessions.
Target discovery. To manage dynamic infrastructure users will need a way to discover and add newly provisioned hosts to targets while enforcing existing access policies on new instances. With Boundary 0.1, you can provision these targets and access policies dynamically with the
Boundary Terraform provider. In the releases following launch we'll give administrators the ability to define dynamic host catalogs to discover new hosts based on predefined rules or tags for
Consul, each of the major cloud platforms, and Kubernetes.