LakeQL
  • Overview
Server Setup
  • Create Server
  • Define Config
  • Yoga Configuration
  • createLakeQLApp
Authentication
  • Authorization Model
  • JWT Authentication
  • Permissions
  • Scope Authorization
  • Trino User Impersonation
  • Debugging Identity
Schema Builder
  • Builder Configuration
  • Scalar Types
  • Comparison Types
  • Pagination
  • Input Validation
Customization
  • Custom Queries & Mutations
  • Extending Core
  • CORS Configuration
  • Error Handling
  • API Reference
GitHub
LakeQL
  1. API
  2. Authentication

Authentication

Validate tokens, resolve identity, enforce permissions, and impersonate users.

LakeQL authenticates and authorizes every request before a query runs. The authorization model ties the pieces together; the concerns beneath it are JWT validation, permissions, scope authorization, and Trino user impersonation. Each has its own extension point, covered in the pages below.

Authorization Model

How LakeQL's permission rules compose with each data source's own access control.

JWT Authentication

Validate the request token and resolve the current user.

Permissions

Grant technical users scoped read and write access per table.

Scope Authorization

How LakeQL authorizes fields through Pothos scope-auth.

Trino User Impersonation

Run Trino queries as the authenticated user.

Debugging Identity

Observe which identity and credential a request runs as, and why removing impersonation silently changes it.

Previous page

createLakeQLApp

Next page

Authorization Model