From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: LDAP auth |
Date: | 2006-03-06 08:54:21 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA350C6@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
> Andrew Dunstan wrote:
> > I suggested libcurl in another context, and not so much as
> a means of
> > getting at LDAP data as a means of getting config data from
> non-LDAP
> > as well as LDAP sources. If all we want is LDAP then using libcurl
> > would indeed be introducing an unnecessary dependency.
> >
> > In this context, though, its use seems a bit odd.
>
> Right, that's what I remember, the curl can _also_ be used to
> distribute authentication data, but of course LDAP is more standard.
Um. LDAP is a protocol, curl is a libary. I assume you mean OpenLDAP,
though. And yes, OpenLDAP is way more common than libcurl for getting
LDAP data. And since libcurl depends on openldap, there's really no
point in donig it unless you're going to use the *other* features of
libcurl as well.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Karasik | 2006-03-06 09:12:27 | Re: implement prepared queries in plperl |
Previous Message | Magnus Hagander | 2006-03-06 08:30:45 | Re: [HACKERS] LDAP auth |