Re: Best practice? Web application: single PostgreSQL

Поиск
Список
Период
Сортировка
От scott.marlowe
Тема Re: Best practice? Web application: single PostgreSQL
Дата
Msg-id Pine.LNX.4.33.0401131051350.22609-100000@css120.ihs.com
обсуждение исходный текст
Ответ на Best practice? Web application: single PostgreSQL user vs. multiple users  ("Keith G. Murphy" <keithmur@mindspring.com>)
Ответы Re: Best practice? Web application: single PostgreSQL  (Keith Murphy <keithmur@mindspring.com>)
Re: Best practice? Web application: single PostgreSQL  (Martin Marques <martin@bugs.unl.edu.ar>)
Список pgsql-general
On Tue, 13 Jan 2004, Keith G. Murphy wrote:

> I'm trying to get a feel for what most people are doing or consider best
> practice.
>
> Given a mod_perl application talking to a PostgreSQL database on the
> same host, where different users are logging onto the web server using
> LDAP for authentication, do most people
>
> 1) have the web server connecting to the database using its own user
> account (possibly through ident), and controlling access to different
> database entities strictly through the application itself
>
> 2) have the web server connecting to the database actually using the
> user's account (possibly using LDAP authentication against PostgreSQL),
> and controlling access to different database entities through GRANT, etc.
>
> Obviously, (2) leads to more database connections, and you still have to
> have the application do some work in terms of which forms are available
> to which users, etc.  But I'm a little worried about whether it's best
> security practice.

I do 1.  different language (PHP) same basic thing though.  All security
is handled by ACLS I build myself in Postgresql and interrogate via my own
application.


В списке pgsql-general по дате отправления:

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: Postgress and MYSQL
Следующее
От: "Chris Ochs"
Дата:
Сообщение: Pl/Perl speed