Re: User Authentication: LDAP and "local" accounts concurrently ?

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: "Lentes, Bernd" <bernd(dot)lentes(at)helmholtz-muenchen(dot)de>
Cc: pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: User Authentication: LDAP and "local" accounts concurrently ?
Date: 2018-11-23 19:14:13
Message-ID: 20181123191413.GJ3415@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Greetings,

* Lentes, Bernd (bernd(dot)lentes(at)helmholtz-muenchen(dot)de) wrote:
> ----- On Nov 23, 2018, at 4:17 PM, Stephen Frost sfrost(at)snowman(dot)net wrote:
> > * Lentes, Bernd (bernd(dot)lentes(at)helmholtz-muenchen(dot)de) wrote:
> >> i created a Postgres Server 9.6 on a SLES 12 SP3 box. In our institution we have
> >> a Windows ADS which i like to use to authenticate users via LDAP.
> >
> > For running PostgreSQL in a Windows ADS environment, you should really
> > be using GSSAPI / Kerberos and *not* using LDAP authentication.
> >
> > GSSAPI / Kerberos is what Windows uses to authenticate users and
> > services and it's much more secure than using LDAP.
>
> thanks for your answer. I'm not familiar with LDAP, GSSAPI and Kerberos.
> Why is it more secure ?

With LDAP, the user's password will be seen by the PostgreSQL server,
and sent over the wire in cleartext unless you're making sure to use TLS
on the connection to PG (and if you're doing that you really want to
make sure you have verify-full enabled on your clients....).

With Kerberos/GSSAPI, the authentication tokens are encrypted by the KDC
(in your case, the AD domain controllers) and the user's password is
never exposed.

Thanks!

Stephen

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Lentes, Bernd 2018-11-23 21:38:35 Re: User Authentication: LDAP and "local" accounts concurrently ?
Previous Message Lentes, Bernd 2018-11-23 18:57:13 Re: User Authentication: LDAP and "local" accounts concurrently ?