Skip to main content
How-to guideApplies to: Unified engine deployments
Keep a bearer token in a named secret. A credential refers to that secret, and a catalog connection refers to the credential.

Have a working token ready

Use an existing Iceberg REST catalog that accepts bearer tokens and exposes the SF1 item table in tpcds_sf1. Replace its URL, warehouse, namespace, and token below. This recipe does not obtain or renew the token. The catalog must supply usable temporary S3 credentials, or you need a separate storage credential. The engine needs the local encrypted secret store described in the recipe overview.

Give the token a stable name

SHOW and DESCRIBE return the name, source, and revision. They do not return the token. The SECRETS value is the saved secret’s name, not the token text.

Use it in a connection

The SELECT should return item rows. It checks both catalog access and file access. Saving the credential alone does not perform either check. Remove the registration before its credential and secret when finished:
Last modified on November 4, 2026