From trust to Tokens: A Short History of PostgreSQL Authentication | POSETTE 2026

Murat Tuncer walks through how PostgreSQL authentication evolved from early trust-based local setups to modern certificate and token-based approaches, explaining why each method exists, what trade-offs it made, and the common mistakes teams still run into when choosing auth for production deployments.

Overview

This POSETTE 2026 talk gives a story-driven tour of PostgreSQL authentication methods, focusing on the key inflection points that shaped today’s options and how those historical decisions still show up in real-world deployments.

What the talk covers

The core problem PostgreSQL authentication is trying to solve

Early Unix-centric assumptions

The presenter starts with early approaches that fit local, Unix-style deployments:

These methods reflect assumptions about local users and host trust boundaries that don’t always hold in modern distributed systems.

Password authentication and its trade-offs

Enterprise authentication integrations

As PostgreSQL became common in larger organizations, it gained integrations that fit enterprise identity systems:

The talk focuses on why these options exist and what problems they were intended to solve.

Certificate-based authentication

Token-based authentication in the cloud era

Practical guidance

Choosing an authentication method

Common mistakes