Authentication

Both your local tipi CLI installation as well as your tipi.build cores and nodes require access to your tipi account to be able to access private repositories and your subscription information.

In order to enable a frictionless usage tipi comes with a crendetials store dubbed tipi vault which is essentially a zero-knowledge encrypted storage linked to your account.

Creating of the vault

During the onboarding on tipi.build you will be asked to create said vault and to provide a passphrase for it. That passphrase is used during the browser session to encrypt the vault and is never sent to our servers.

In the following onboarding steps you will be given the opportunity to grant your account access to private repositories on Github.com which is required if you want to consume privatly listed dependencies.

That access can be granted at any time using the vault dashboard on tipi.build.

Authenticating to tipi.build with tipi CLI

Run the tipi connect command and follow the instructions. You will be prompted with a link to authenticate the device on tipi.build. After confirming the access to your vault the CLI will ask for your vault passphrase.

For private cloud and on premise users: you can connect to your private deployment of tipi.build by specifying the TIPI_ENDPOINT environment variable

Authentication in Continuous Integration context

On non-interactive usages of tipi credentials can be provided by setting the following environment variables: TIPI_ACCESS_TOKEN, TIPI_REFRESH_TOKEN, TIPI_VAULT_PASSPHRASE.


Found an error or want to add more info? Write an issue or contribute changes to this documentation at tipi-build/docs on