From: | "Roland Giesler" <roland(at)giesler(dot)za(dot)net> |
---|---|
To: | "'Kevin Crenshaw'" <kcrenshaw(at)viscient(dot)com>, <brew(at)theMode(dot)com>, <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Best way to manage users |
Date: | 2006-01-04 17:43:39 |
Message-ID: | TAXNET01EsBk31TZ14e0000016c@frontdoor.taxpoint.co.za |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Kevin Crenshaw wrote:
> Thanks for the replies. I appreciate the advice. However, I
> think that a better way to pose my question is to ask - what
> are the pros and cons of using Postgres to handle user
> authentication for my web app?
Maybe to add to that question: Is there a way to directly authenticate a
user as a database user when using a web app? In .net, this is handeled by
a cobination of the OS (active directory - AD), the DB (SQL Server) which
can authenticate against AD, and the browser. However, how can pg get or
request the authentication from your webbrowser? Unless there is a pgsql
function that allows login as a different user from a webapp from the
webapp, I would think it's not possible to actually do this the way a
statefull app does it (under windows for example)
Some comments on this would be great, as I have a very similar requirement
and was also toying with the idea of using the pg users, instead of creating
my own tables and user authentication infrastructure.
Thanks
Roland Giesler
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Witney | 2006-01-04 17:47:09 | Re: Best way to manage users |
Previous Message | Sean Davis | 2006-01-04 17:36:55 | Re: Best way to manage users |