pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Daniel Gustafsson <dgustafsson@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Explicitly require password for SCRAM exchange
Date: Thu, 21 Mar 2024 14:08:55 +0000
Message-ID: <E1rnJ6F-004wum-BC@gemulon.postgresql.org> (raw)

Explicitly require password for SCRAM exchange

This refactors the SASL init flow to set password_needed on the two
SCRAM exchanges currently supported. The code already required this
but was set up in such a way that all SASL exchanges required using
a password, a restriction which may not hold for all exchanges (the
example at hand being the proposed OAuthbearer exchange).

This was extracted from a larger patchset to introduce OAuthBearer
authentication and authorization.

Author: Jacob Champion <jacob.champion@enterprisedb.com>
Discussion: https://postgr.es/m/d1b467a78e0e36ed85a09adf979d04cf124a9d4b.camel@vmware.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/adcdb2c8dda4fb28e373ddff41a0de6936772249

Modified Files
--------------
src/interfaces/libpq/fe-auth.c | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)



Message-ID: <E1rnJ6F-004wum-BC@gemulon.postgresql.org>
Permalink:  ../E1rnJ6F-004wum-BC@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1rnJ6F-004wum-BC@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: dgustafsson@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Explicitly require password for SCRAM exchange
  In-Reply-To: <E1rnJ6F-004wum-BC@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox