Skip to content

Update from code changes: TLS enforcement on the Metrics SQL API#1029

Open
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/8362578f
Open

Update from code changes: TLS enforcement on the Metrics SQL API#1029
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/8362578f

Conversation

@mintlify

@mintlify mintlify Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Clarify that the self-hosted Metrics SQL API (pgwire) endpoint requires TLS by default and document the boot-time validation, cert hot-reload, StartTLS constraint, and the client-side rejection behavior.

Changes

  • Note the boot-time config error when PGWIRE_PORT is set without certs and without an explicit opt-out.
  • Document the cert/key file watcher: renewals apply without a restart, failed reloads keep the previous context.
  • Warn that the pg StartTLS handshake means the endpoint cannot sit behind a generic TLS-terminating load balancer.
  • Add the exact rejection a sslmode=disable client sees (connection requires TLS, SQLSTATE 28000) with guidance to switch to sslmode=require.

Context

Follows lightdash/lightdash#25615, which makes TLS the default on the pgwire semantic layer endpoint so personal access tokens never cross the network in plaintext.

@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

🤖 Documentation Bot

All checks passed! No issues found.

@mintlify
mintlify Bot requested a review from owlas July 17, 2026 00:45
@mintlify

mintlify Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
lightdash 🟢 Ready View Preview Jul 17, 2026, 12:47 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant