Re: [PATCHES] LDAP auth

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] LDAP auth
Date: 2006-03-06 19:29:54
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA0F833@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> >> If your patch is accepted and a dependency on OpenLDAP is
> introduced,
> >> my patch will provide an additional gain with no additional cost.
> >
> > Out of curiosity what would an SQL database want with ldap anyways?
> > Is it just a set of bindings for ldap functions for applications?
>
> No, what I have in mind is a way to lookup database
> connection options (dbname, port, etc.) on an LDAP server, so
> that the connection information can be stored in one central
> place and does not have to be distributed to the clients.
>
> BTW, I checked the Windows API for LDAP, and it is quite
> different from OpenLDAP. So I'm afraid that I'll have to use
> OpenLDAP on Windows too :^(

Please look at that once more. There are serious integration issues
using OpenLDAP on windows - at least if you want to put SSL into the
mix. And it's not really that different. You might also want to take a
look at the code from dblink-ldap, which runs fine on both Windows and
linux, without a huge amount of #ifdefs.
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/dblink-ldap/dblink-ldap/dbl
ink-ldap.c?rev=1.3&content-type=text/x-cvsweb-markup)

//Magnus

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Bertheau 2006-03-06 19:58:27 Plan for resetting commented postgresql.conf vars at sighup
Previous Message Peter Eisentraut 2006-03-06 19:16:50 Re: PostgreSQL Anniversary Summit, Call for Contributions