Fuzzball Documentation
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Secret Scope

Every Fuzzball secret carries a scope that determines who can use it.

  • user – available only to the user who created it. Any user can create one.
  • group – available to every member of the group. Only group owners can create one.
  • organization – available across the organization. Only organization owners can create one.
  • cluster – reserved for system-level secrets. Creating, showing, updating or deleting one requires cluster administrator privileges and goes through the administrative API rather than the ordinary one. The CLI accepts a cluster secret’s name or its UUID. Names beginning with user-token- are reserved for secrets Fuzzball keeps for itself, and cannot be used. Each of these calls that reaches the service, and listing them, is recorded in the audit log without the secret’s value, including a call refused because the caller is not a cluster administrator.

Fuzzball addresses every secret by a reference of the form secret://<scope>/<name> – for example, secret://user/my-user-s3-secret. Workflows name the secrets they need by this reference; see Using Secrets in Workflows for how to use one.

The account scope is accepted as a legacy alias for group in both the CLI (-s account) and secret reference URIs (secret://account/<name>). New secrets should use group.