Type '/' to Search

»Run and Login to Boundary

To start Boundary in dev mode:

$ boundary dev

$ boundary dev

»Login to Boundary

Boundary uses a predictable login name (admin) and password (password) in dev mode. These can be overridden, or randomly generated, with flags to boundary dev.

$ boundary authenticate password \
         -login-name=admin \
         -password password \
         -auth-method-id=ampw_1234567890

$ boundary authenticate password \
         -login-name=admin \
         -password password \
         -auth-method-id=ampw_1234567890

If you are on Windows or macOS, the system password store will be used to store the new token. On any other operating system, you may get an error indicating that the token could not be stored. Boundary defaults to using pass on these machines, which uses GNU Privacy Guard to encrypt values. If it is not available, the token will be displayed and can be stored in a system of your choice and passed in via the BOUNDARY_TOKEN environment variable.

It is recommended to make use of pass or another alternative (such as any implementation of the freedesktop.org Secret Service feature). Installation and configuration of pass or other alternatives is beyond the scope of this article; consult the documentation for pass or your specific OS distribution help pages.

»Next Steps

See connecting to your first target for how to use Boundary to run your first SSH session.