PostgreSQL: Add Kerberos/GSSAPI integrated authentication (Windows SSPI)

[stichak]

PostgreSQL: Add Kerberos/GSSAPI integrated authentication (Windows SSPI)

Feature request

Please add Kerberos/GSSAPI authentication support for PostgreSQL connections, including integrated Windows authentication through SSPI.

Use case

Our PostgreSQL servers are configured to authenticate domain users through Kerberos (gss in pg_hba.conf). Users already have a valid Windows domain session and can connect with Kerberos-capable PostgreSQL clients without entering or storing a separate PostgreSQL password.

DBCode currently appears to require username/password authentication for PostgreSQL, so it cannot be used in this environment.

Desired behavior

Add an authentication option such as:

• Kerberos / GSSAPI
• Use current Windows credentials (SSPI)

Ideally, the connection should support:

• credentials from the current Windows logon session;
• PostgreSQL service principals such as postgres/server.example.com@REALM;
• optional Kerberos principal and service-name configuration;
• existing Kerberos ticket caches on Linux and macOS;
• SSL combined with GSSAPI authentication.

Why this matters

Many enterprise and university environments prohibit database passwords or use centrally managed Active Directory/Kerberos identities. Integrated authentication would allow DBCode to be used without creating separate password-based PostgreSQL accounts or storing database credentials.

Environment

• Client: VS Code + DBCode on Windows
• Database: PostgreSQL configured with Kerberos/GSSAPI
• Identity provider: Active Directory