Skip to content
Riptides Docs

Credentials

The Credentials screen lists your credential sources: where Riptides obtains or stores the secrets and tokens it delivers to workloads. A credential source defines how a credential is produced (a static secret, a short-lived cloud token, an OAuth2 token, a Vault secret, and so on). A Credential Binding then delivers it to a workload.

Open it from Configure → Credentials in the sidebar (/ui/credential-sources).

What you see

Section titled “What you see”

Three cards summarize your credentials (source status, credentials by type, and bindings by credential type). The table lists each source with:

  • Status: Active or Inactive.
  • Name.
  • Type: the kind of source (see below).
  • Assigned Identities: the workload identities using it.

Search by name and filter by Type. Each row’s ⋯ menu offers Edit and Delete (Delete is blocked while bindings still use the source).

Add a credential

Section titled “Add a credential”

Choose Add Credential, give it a Name and optional Description, then pick a Type. The form then shows only the fields for that type:

  • Riptides Static Secret: a stored bearer token or API key. You provide its Value.
  • Riptides JWT SVID: short-lived signed JWTs, for services that accept OIDC-style tokens. You set the Audience and optional lifetime and claims.
  • AWS / Google Cloud / Azure / OCI Token Exchange: exchange the workload’s identity for temporary cloud credentials. You provide the role or provider details for that cloud.
  • OAuth2 Client Credentials and OAuth2 Authorization Code: fetch tokens from any OAuth2 endpoint, using the client-credentials or authorization-code flow.
  • Vault / OpenBao: fetch a secret from HashiCorp Vault or OpenBao, authenticating with the workload’s JWT.

Edit, delete, and detail

Section titled “Edit, delete, and detail”

Edit or delete a source from its row ⋯ menu. Clicking a source opens a detail panel with its configuration and a Credential Bindings table showing the workloads currently bound to it.

Next steps

Section titled “Next steps”
Privacy policy Cookie policy