Re: Validating User Login Within Postgres - Mailing list pgsql-general

From Sim Zacks
Subject Re: Validating User Login Within Postgres
Date
Msg-id 53B39A79.3050503@compulab.co.il
Whole thread Raw
In response to Re: Validating User Login Within Postgres  (Rich Shepard <rshepard@appl-ecosys.com>)
List pgsql-general
<div class="moz-cite-prefix">On 07/01/2014 06:03 PM, Rich Shepard wrote:<br /></div><blockquote
cite="mid:alpine.LNX.2.11.1407010757070.21028@localhost"type="cite">On Tue, 1 Jul 2014, hubert depesz lubaczewski
wrote:<br /><br /><blockquote type="cite">That depends. For example - for system that will have 5 users, and <br />
requiresstrict security policies - it would make sense. On the other <br /> hand, for website, with thousands of users,
puttingthem all as actual <br /> roles in Pg doesn't make much sense, and could potentially cause problem. <br
/></blockquote><br/> Hubert, <br /><br />   OK. This is not a Web-based application, but the users could number in the
<br/> dozens. <br /></blockquote> Using database user authentication is great for corporate use. If you have an LDAP
(oractive directory) you can define the authentication to use that. See the pg_hba file for details on various
authenticationmethods. <br /><br /> Our application is written in python as well (desktop modules in wxPython and web
modulesin django)  and we use LDAP authentication.<br /><br /> sim<br /> 

pgsql-general by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: pl/perl and recent perl versions - failing to load internal modules
Next
From: Arup Rakshit
Date:
Subject: How can I replace the year of the created_at column with the current year dynamically ?