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-07 07:56:53 |
Message-ID: | 52EF20B2E3209443BC37736D00C3C1380734B3DA@EXADV1.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>I find it hard to imagine LDAP being sensibly use for any other
postgres
>>>purpose than authentication, despite recent flights of fancy on the
list
>>>about storing large slabs of config data there.
>>
>>It can also make sense to get authorization information from LDAP.
>
> Yes, that's true. But I can imagine putting a shared config setup on a
> web server, or an ftp server, or a tftp server, a good deal more
easily
> than putting it in LDAP.
I don't want to discuss matters of taste, and this is clearly such a
matter.
I tend to agree that it is a little exaggerated to set up an LDAP server
just to store a few bits of connection information.
But nowadays LDAP servers are used for various things, like directories
of employees, and if you already have an LDAP server in the house, it is
the
perfect tool for the task.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-03-07 08:48:57 | FW: PGBuildfarm member snake Branch HEAD Status changed from OK to PLCheck failure |
Previous Message | Tom Lane | 2006-03-07 07:50:40 | Re: PostgreSQL Anniversary Summit, Call for Contributions |