pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: greatvovan@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: User mapping security
Date: Thu, 9 Nov 2023 17:02:53 -0500
Message-ID: <ZU1XDU7dWU1zLLv2@tamriel.snowman.net> (raw)
In-Reply-To: <ZU1SOvgnwbBawgzN@momjian.us>
References: <156324246053.1191.5972769566826595079@wrigleys.postgresql.org>
	<ZU1SOvgnwbBawgzN@momjian.us>

Greetings,

* Bruce Momjian (bruce@momjian.us) wrote:
> On Tue, Jul 16, 2019 at 02:01:00AM +0000, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> > 
> > Page: https://www.postgresql.org/docs/10/postgres-fdw.html
> > Description:
> > 
> > Regarding the documentation pages
> > https://www.postgresql.org/docs/10/postgres-fdw.html?origin_team=T02HEPYKQ
> > and https://www.postgresql.org/docs/10/sql-createusermapping.html
> > 
> > I suppose it should be warned on the pages that foreign credentials with be
> > stored as simple text and will be available for viewing in pg_user_mappings.
> 
> I know this is four years old, but the attached patch documents it.  I
> don't think postgresql-fdw needs it since it relies on user mapping and
> discourages passwords in the connection string.

A bit on the fence about it ... but I do wonder if we should encourage
use of gssapi and credential delegation now that we support that and
point out that storing passwords isn't required if you're using gssapi.

Thanks,

Stephen

> diff --git a/doc/src/sgml/ref/create_user_mapping.sgml b/doc/src/sgml/ref/create_user_mapping.sgml
> index 55debd5401..e93bfe48f6 100644
> --- a/doc/src/sgml/ref/create_user_mapping.sgml
> +++ b/doc/src/sgml/ref/create_user_mapping.sgml
> @@ -92,7 +92,11 @@ CREATE USER MAPPING [ IF NOT EXISTS ] FOR { <replaceable class="parameter">user_
>        This clause specifies the options of the user mapping.  The
>        options typically define the actual user name and password of
>        the mapping.  Option names must be unique.  The allowed option
> -      names and values are specific to the server's foreign-data wrapper.
> +      names and values are specific to the server's foreign-data
> +      wrapper.  Option values, including passwords, are visible in the
> +      <link
> +      linkend="catalog-pg-user-mapping"><structname>pg_user_mapping</structname></link>
> +      system view.
>       </para>
>      </listitem>
>     </varlistentry>

Attachments:

  [application/pgp-signature] signature.asc (832B, ../ZU1XDU7dWU1zLLv2@tamriel.snowman.net/2-signature.asc)
  download

view thread (5+ messages)  latest in thread

Message-ID: <ZU1XDU7dWU1zLLv2@tamriel.snowman.net>
Permalink:  ../ZU1XDU7dWU1zLLv2@tamriel.snowman.net/
Also on:    postgresql.org/message-id/ZU1XDU7dWU1zLLv2@tamriel.snowman.net

 · 

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-docs@postgresql.org
  Cc: sfrost@snowman.net, bruce@momjian.us, greatvovan@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: User mapping security
  In-Reply-To: <ZU1XDU7dWU1zLLv2@tamriel.snowman.net>

* 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