HashiCorp Boundary Identity changes how secure access works in dynamic infrastructure. Instead of static credentials, it uses identity-based access. Every request is authenticated against a trusted identity provider. Permissions are tied to who you are, not to where you log in from or what secret you know. This removes the need to share SSH keys or rotate database passwords between teams.
Boundary connects to identity providers like Okta, Azure AD, and others through OpenID Connect (OIDC). This allows centralized user lifecycle management. Add a user in your IdP, assign roles in Boundary, and access is instantly available across multiple targets. Remove a user, and all their access disappears in real time.
Identity in HashiCorp Boundary is more than authentication. It defines roles, scopes, and grants. Roles group permissions for one or more scopes—logical units like projects or environments. Grants specify what actions a role can perform, from listing resources to connecting to a specific target system. Combined, this model makes it possible to delegate fine-grained, least-privilege access across infrastructure, without distributing secrets.