Skip to main content
How-to guideApplies to: Unified engine deployments
Send an existing access token to an Iceberg REST catalog. A bearer credential uses token text from a secret reference; it does not perform an OAuth login.

Prepare the token and catalog

Use an existing catalog that accepts your token and exposes an SF1 item table. Replace the URL, warehouse, namespace, and token below. The token must already have the required catalog permissions. The catalog must supply usable temporary S3 credentials, or use a separate storage credential. The local encrypted secret store must be available.

Attach the token by name

Use the raw token, not a JSON object containing it. If the token is already held by a configured external provider, replace the CREATE SECRET statement with a reference such as CREATE SECRET recipe_bearer_token USING 'recipe_ssm:///laminar/recipes/catalog-token' after completing that provider’s setup. Saved bearer tokens are not renewed automatically. Obtain a replacement from the issuer and rotate the secret, or use an OAuth credential when the service supports it. When finished:
Last modified on November 4, 2026