Skip to main content

Credentials

Credentials store the connection details your tasks use to reach third-party systems such as Jira, Slack or AWS. Create, test and share them, and attach them to projects. The integration catalog lists the vendors Jaah connects to, starts a vendor's one-click Connect and takes votes for vendors; the NodeVault endpoints set up, rotate and migrate the key that seals credentials only your organization's nodes can open.

๐Ÿ“„๏ธStart integration connect

Starts a one-click OAuth Connect for a catalog vendor or a forge without saving a credential first, and returns the consent URL; the credential is created when the vendor redirects back. The body names it (`name`, optional for a forge), who it belongs to (`owner`), the projects to attach it to and optionally your own OAuth app; a forge (`github`, `gitlab`, `bitbucket`, `azure_devops`) is always your own personal connection on Jaah's app, landing on `return_to` with GitHub's app picked by `app`. Returns 409 (GitHub: 503) while Jaah's app is not set up and no client was given, and 404 for a vendor without OAuth.

๐Ÿ“„๏ธStart NodeVault rotation

Starts a NodeVault rotation with a new public key, its confirmed backup, and the new private key wrapped under the current NodeVault key (`chain_blob`); returns 202 with the operation id, and nodes keep the old key until it is retired. Returns 422 when `chain_blob` is not wrapped under the current key, and 409 when NodeVault is not set up, no node holding the current key is online, or another NodeVault operation runs (with its `operation_id`). Requires the Org Owner or Org Admin role and a plan that includes NodeVault.

๐Ÿ“„๏ธStart NodeVault setup

Starts NodeVault setup with a new public key, its confirmed backup, and the key wrapped to each capable node; returns 202 with the operation id. Returns 422 with `missing` and `extra` node ids when the wrapped keys do not cover exactly the capable nodes, and 409 when no capable node is online, NodeVault is already set up, or another NodeVault operation runs (with its `operation_id`). Requires the Org Owner or Org Admin role and a plan that includes NodeVault.