A web UI must call an agent without exposing tokens in the browser. What fits?
Why C is the answer
A Databricks App backend
A backend keeps tokens server-side and enforces identity.
In detail
- A backend keeps tokens on the server side.
- A Databricks App can also apply each user's identity.
- Apply each user's identity in the backend.
Use case
An illustrative scenario, not a real incident.
A web chat must call an agent. A Databricks App backend holds the credentials and checks each user, so no token ever reaches the browser.
See it in different ways
sequenceDiagram participant A as Agent participant B as Databricks Secrets participant E as External MCP server A->>B: Read the secret reference B-->>A: Key at run time A->>E: Tool call, authenticated
sequenceDiagram participant P0 as Browser participant P1 as Databricks App participant P2 as Agent P0->>P1: Signed-in request P1->>P2: Call with credentials P2-->>P1: Reply P1-->>P0: Result
Key point: Tokens stay on the server.
Why the other options are wrong
- A. A public endpoint with an API key in the page
- A key in the page is public.
- B. A public bucket of source files
- A public bucket exposes data, and it does not call an agent.
- D. A personal access token in the JavaScript
- JavaScript sends the token to every browser.