Skip site navigation (1) Skip section navigation (2)

Re: new feature: LDAP database name resolution

From: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>
To: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: new feature: LDAP database name resolution
Date: 2006-02-28 15:33:44
Message-ID: 52EF20B2E3209443BC37736D00C3C1380718AA72@EXADV1.host.magwien.gv.at (view raw or flat)
Thread:
Lists: pgsql-hackers
>>I have added a configure option --with-openldap to enable the code.
>>
>>Does that make sense to you?
>>
>>Should I try to polish and test the code and submit it as a patch
> 
> I would still much prefer to see remote config fetching done in a more

> general way, using say libcurl (which handles ldap just fine if
openldap 
> is available). Then we could fetch the config from a variety of
sources, 
> not just ldap. Libcurl uses a modified MIT license, so we should not 
> have any problems on that score. And with luck it would involve less 
> postgres code maintenance.

So if I make the effort to modify the LDAP support to curl support,
would the community be interested?

Since we here use only LDAP, I would only want to embark on this if
you want to add it to PostgreSQL (if my code is good enough,
of course).

Yours,
Laurenz Albe

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-02-28 15:35:53
Subject: Re: new feature: LDAP database name resolution
Previous:From: Tom LaneDate: 2006-02-28 15:28:33
Subject: Re: Dead Space Map

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group