Message-ID: <c24aeecbfe49b3106fa538cabfe34a100cf3081f.camel@cybertec.at>
Subject: Re: unrecognized configuration parameter "ldapbinddn" in file
 "/var/lib/pgsql/data/postgresql.conf"
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Bernd Lentes <bernd.lentes@helmholtz-muenchen.de>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Thu, 02 Nov 2023 21:37:23 +0100
In-Reply-To: 
 <PR3PR04MB7340275A4B83BB8BFD48F37BD6A6A@PR3PR04MB7340.eurprd04.prod.outlook.com>
References: 
	<PR3PR04MB7340275A4B83BB8BFD48F37BD6A6A@PR3PR04MB7340.eurprd04.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/c24aeecbfe49b3106fa538cabfe34a100cf3081f.camel%40cybertec.at>
Precedence: bulk

On Thu, 2023-11-02 at 19:56 +0000, Bernd Lentes wrote:
> i'm trying to use LDAP to authenticate Postgres against a Windows AD. On =
elder versions it succeeded.

Possible ...

> Now I'm running postgresql-15-150500.8.19.noarch on a SLES 15 SP5 system.
> I can't start the db server because it doesn't know the respective config=
uration parameters:
>=20
> LOG:  unrecognized configuration parameter "ldapbinddn" in file "/var/lib=
/pgsql/data/postgresql.conf" line 106
> [...]
> FATAL:  configuration file "/var/lib/pgsql/data/postgresql.conf" contains=
 errors

... but in those older versions you couldn't have had the parameter in "pos=
tgresql.conf".

They belong in "pg_hba.conf"; see the documentation:
https://www.postgresql.org/docs/current/auth-ldap.html

Yours,
Laurenz Albe