> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to Lakekeeper using a bearer token

> Register Lakekeeper in Unified and read an existing table with a bearer token.

How-to guideApplies to: Unified engine deployments

Register Lakekeeper in Unified and read an existing table with a bearer token.

## Before you start

Use an existing catalog with at least one readable Iceberg table. The engine and
workers must reach the catalog and its table storage. Have the remote identity
and permissions ready before creating the Unified registration. Replace the
namespace and table with one you know has data.

Collect the Lakekeeper catalog API URI and warehouse identifier. The no-auth
variant is for an instance explicitly configured to allow it; it does not
disable server authentication.

The service must return usable temporary storage credentials, or the table
location must already have configured storage access in Unified. Requesting
delegation alone does not grant access. Local secret values require the
[encrypted secret store](https://docs.e6data.com/transformation/operations/configuration/secrets.md).

## Values to collect

* Catalog API URI, warehouse, namespace, and table.
* A valid access token accepted by this service.

## Run the SQL

Replace every `<placeholder>` before running. Use unused names for the resources
below. Run the statements in order in Workbench.

```sql theme={"theme":{"light":"github-light","dark":"github-dark"}}
CREATE SECRET recipe_lakekeeper_bearer_secret AS '<access-token>';

CREATE CREDENTIAL recipe_lakekeeper_bearer_auth USING bearer
OPTIONS (
  'authentication' = 'saved'
)
SECRETS ('token' = 'recipe_lakekeeper_bearer_secret');

CREATE CATALOG recipe_lakekeeper_bearer USING `iceberg-rest`
OPTIONS (
  'uri' = '<catalog-api-uri>',
  'warehouse' = '<warehouse>',
  'catalog.type' = 'lakekeeper',
  'auth.type' = 'bearer',
  'header.x-iceberg-access-delegation' = 'vended-credentials'
)
CREDENTIALS ('auth' = 'recipe_lakekeeper_bearer_auth');

SELECT *
FROM recipe_lakekeeper_bearer.`<namespace>`.`<table>`
LIMIT 5;
```

## Check the result

The SELECT should return up to five rows from the chosen table. Use a nonempty
table for this check. This verifies both metadata and table-file access;
creating the registration alone does not verify either.

## Clean up

This removes only the Unified registrations. It leaves the remote catalog and
its tables in place.

```sql theme={"theme":{"light":"github-light","dark":"github-dark"}}
DROP CATALOG recipe_lakekeeper_bearer;
DROP CREDENTIAL recipe_lakekeeper_bearer_auth;
DROP SECRET recipe_lakekeeper_bearer_secret;
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.