Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1idDTJ-0008Vr-2Z for pgsql-docs@arkaria.postgresql.org; Fri, 06 Dec 2019 13:16:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1idDTF-0003eI-6V for pgsql-docs@arkaria.postgresql.org; Fri, 06 Dec 2019 13:16:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1idDTE-0003eB-R8 for pgsql-docs@lists.postgresql.org; Fri, 06 Dec 2019 13:16:32 +0000 Received: from mail-lf1-x132.google.com ([2a00:1450:4864:20::132]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1idDT8-0004Mr-0t for pgsql-docs@lists.postgresql.org; Fri, 06 Dec 2019 13:16:32 +0000 Received: by mail-lf1-x132.google.com with SMTP id r14so5247765lfm.5 for ; Fri, 06 Dec 2019 05:16:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Uyri9gVaJz3aONx7lNrfGTDntJ6w2ZFRGfuav5ZWKIc=; b=jRT+4any/+JIFoNAxzJ07TuYH4hfYZUrQeJjkd87yjNphxD9PokuOwuSMDUTOtr4Ga Q1VUmIjtGPV9zn/k7vmtEuUFleW7SHwrkT1nagNUBBVc3pv0GLy45pFjIti1Qh2gpNcd MYdADgNVc4KiuRAhnPByEyyMZhjf1tHpQEjzrPBY55hXv6X3urYqew+Kp2TV0SW6GRH/ YvKyKh+49yqnyJJvl88eYnWYMXk55eS/M/S7x8MyvyogeT3e9UubQw0lP2nwfNQLomJm lyVJXPaGHtvhBwIBnLZVEtXcQp0m1ANdMYF8A7GttN2CDmTbTDtTy8aa2jmvQrjGi9we kPcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Uyri9gVaJz3aONx7lNrfGTDntJ6w2ZFRGfuav5ZWKIc=; b=eo4yX4aie55pr7AqZSWuFl1uH/+GpF9Pudme9EVXahcjHA4x7lQ1L+T6WwBPIe3sZc l5fFeT4pwKUcLmF6t3D4/DRB6wZej/WXm+zlMFJisg8dVSqoyeAi4y29fzstiZe1p6at I/VnExEtP/2qRJSJXJVMtyAiiakuu11nQ/YybYAuwgNyX9/cxbufLXvd6gTurLrNKvb2 Bu7s6y+5C/QaGoK92L8gxAAtpLQpNOp3KDzQv3nimnVVF65jM77UCEbIc9FoKviYni5k gzyVZ7fvYUxbMQQRmLr+goPXrXBVBsl9X1qn6qmsEbc89y2SHF16ap94tJk4QDqS9b7E kRJA== X-Gm-Message-State: APjAAAVYKXmOWwR7T7mQ70ctJsOq47sbviOGcrCAMS3KEMVdGLei186T OTtyRlP53HZS8HwjhSfPln1oHoek41Hxsrxc1gS9Kw== X-Google-Smtp-Source: APXvYqw1jraKW0xs6lxyMFFjv/o4KISLS9B0jn++VpvoTSH7a4F1jkcOxvK/FIUE55WbUdh9t4c7wOPjM7pi2NTQn/o= X-Received: by 2002:ac2:5549:: with SMTP id l9mr8004233lfk.53.1575638183594; Fri, 06 Dec 2019 05:16:23 -0800 (PST) MIME-Version: 1.0 References: <157557861394.25850.9731098233662922606@wrigleys.postgresql.org> In-Reply-To: <157557861394.25850.9731098233662922606@wrigleys.postgresql.org> From: Magnus Hagander Date: Fri, 6 Dec 2019 14:16:12 +0100 Message-ID: Subject: Re: Description of Authentication Methods Supported for Map is Misleading To: kevin.j.hutchison@gmail.com, Pg Docs Content-Type: multipart/alternative; boundary="0000000000003a605d059908dacd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000003a605d059908dacd Content-Type: text/plain; charset="UTF-8" On Fri, Dec 6, 2019 at 10:13 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/auth-pg-hba-conf.html > Description: > > "This option is supported for all authentication methods that receive > external user names." > > More properly, the authentication methods supported are: ident, peer, > gassapi, sspi, and cert. > > LDAP is not supported and attempting to use map with LDAP provides the > following error: > 'authentication option ""map"" is only valid for authentication methods > ident, peer, gssapi, sspi, and cert' > This is correct. LDAP authentication does not receive external usernames. It uses an external service to validate the password, but it gets the username from the client. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --0000000000003a605d059908dacd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Dec 6, 2019 at 10:13 AM PG Doc co= mments form <noreply@postgresq= l.org> wrote:
The following documentation comment has be= en logged on the website:

Page: https://www.postgresql.org/docs/10/aut= h-pg-hba-conf.html
Description:

"This option is supported for all authentication methods that receive<= br> external user names."

More properly, the authentication methods supported are:=C2=A0 ident, peer,=
gassapi, sspi, and cert.=C2=A0

LDAP is not supported and attempting to use map with LDAP provides the
following error:
'authentication option ""map"" is only valid for au= thentication methods
ident, peer, gssapi, sspi, and cert'

This is correct. LDAP authentication does= not receive external usernames. It uses an external service to validate th= e password, but it gets the username from the client.

--
=C2=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-l= inpro.com/
--0000000000003a605d059908dacd--