Skip to content

fix: restore SCRAM as the default auth method over TLS (#1249) - #1256

Merged
v0idpwn merged 1 commit into
RELEASE_2_10from
backport-scram-default-2-10
Oct 30, 2026
Merged

v0idpwn merged 1 commit into
RELEASE_2_10from
backport-scram-default-2-10

Conversation

@v0idpwn

@v0idpwn v0idpwn commented Oct 30, 2026

Copy link
Copy Markdown
Member

Non-JIT clients connecting over TLS had been switched to cleartext password authentication, which breaks clients that only accept SCRAM, such as libpq with require_auth=scram-sha-256. SCRAM is the default again. Cleartext is opt-in through the cleartext_auth_over_tls feature flag (CLEARTEXT_AUTH_OVER_TLS_ENABLED), which replaces scram_auth_over_tls.

(cherry picked from commit 8ac56a2)

Non-JIT clients connecting over TLS had been switched to cleartext
password authentication, which breaks clients that only accept SCRAM,
such as libpq with `require_auth=scram-sha-256`. SCRAM is the default
again. Cleartext is opt-in through the `cleartext_auth_over_tls` feature
flag (`CLEARTEXT_AUTH_OVER_TLS_ENABLED`), which replaces
`scram_auth_over_tls`.

(cherry picked from commit 8ac56a2)
@v0idpwn
v0idpwn requested a review from a team as a code owner October 30, 2026 13:34
@v0idpwn
v0idpwn enabled auto-merge October 30, 2026 13:56
@v0idpwn
v0idpwn merged commit d7856c4 into RELEASE_2_10 Oct 30, 2026
33 of 36 checks passed
@v0idpwn
v0idpwn deleted the backport-scram-default-2-10 branch October 30, 2026 14:21
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.

2 participants