| 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: [PATCHES] LDAP auth |
| Date: | 2006-03-06 16:04:12 |
| Message-ID: | 52EF20B2E3209443BC37736D00C3C1380734AEA8@EXADV1.host.magwien.gv.at |
| 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 :^(
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2006-03-06 16:50:15 | Re: Coverity Open Source Defect Scan of PostgreSQL |
| Previous Message | Greg Stark | 2006-03-06 15:51:25 | Re: [PATCHES] LDAP auth |