Per-role identity
Each Sembric role uses a distinct read-only Trino user over HTTPS with password authentication. Passwords live in runtime secrets and are never entered in the portal.
Integration · Federated SQL engine and lakehouse catalogs
Governed Trino access for AI agents
Discover one Trino catalog and schema, including a lakehouse catalog you operate, and serve certified surfaces through role-specific read-only users.
Identity
How Sembric connects to Trino
Your policies stay in force
Trino’s access-control policy enforces table, column and row restrictions. Sembric does not manage the catalog, ingest rows, create source views or transform data.
Enforcement
What Sembric checks and refuses
- Only exact coordinator origins are allowed, and cross-origin result links are refused.
- Queries use USING parameters and a 30-second client deadline, and check the live schema against the certified fingerprint before execution.
- Every request sets a coordinator-side run-time limit and a physical-scan session setting.
- Each mapped role needs a different username, password variable and underlying secret.
Limits
What these controls don’t do
- The physical-scan setting depends on the connector: a PostgreSQL-backed fixture returns rows despite a 1-byte setting. Neither setting is a cost cap, so enforce source-side resource groups or quotas.
- In an isolated customer plane, serving traffic leaves through a customer-specific NAT address you can allowlist. That gives a stable address, not a destination firewall; verify the observed IP before relying on it.
Setup
Connecting Trino
- Enable HTTPS and password authentication on the coordinator, and create a distinct read-only Trino user for every Sembric role that will receive a grant.
- Enforce table, column and row restrictions in Trino’s access-control policy.
- List the exact coordinator origin on the Sembric runtime and store each role’s password as a runtime secret.
- An owner chooses one catalog and schema, tests every role mapping, then discovers, reviews and certifies.
FAQ
Trino questions
Can Sembric govern a lakehouse through Trino?
Yes. Trino can expose a lakehouse catalog you configure. Sembric discovers that catalog’s schema, and your Trino policies keep enforcing access under each role’s user.
Does the Trino scan setting cap our costs?
No. Its effect depends on the connector, so Sembric does not treat it as a cost control. Use source-side resource groups or quotas.
Other integrations
Put your first certified data product in front of an agent.
Tell us which warehouse you run and what your agents need to answer. We will help you connect a source, certify a first surface and query it over MCP.