Security setup. - Mailing list pgsql-general

From
Subject Security setup.
Date
Msg-id 20110910124246.c760ddbd7c0975bc4b045766db7d895c.268ae380ef.wbe@email16.secureserver.net
Whole thread Raw
Responses Re: Security setup.  (Sim Zacks <sim@compulab.co.il>)
List pgsql-general
<table align="center" bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0" style="empty-cells: show;"
width="100%"><tr><td;=";" </td="</td" align="left" background="cid:top@e13e1eb3de623676fe6c48dabdfd3e15" colspan="1"
height="72"style="text-align: left; background-repeat: no-repeat;"></td></tr><tr><td style="vertical-align: top;"><div
style="padding:5px; overflow-x: auto;"></div></td></tr></table><span style="font-family:Verdana; color:#000000;
font-size:10pt;"><div>Wehave a very solid security appliance which sits in front of our domain controller.  All traffic
fromour users is also controlled via a citrix login and they only have access to the published apps, no
desktops.</div><div><br/></div><div>We have been thinking of using trust as our security method.  If we decide to use
thiswill we be required to enter the users into the database?</div><div><br /></div><div>The other option might be
usingSSL and entering in the users to the db.  We still have to build internal security tables which handle procedure
anddata level security so pushing the login to the database isn't that big of a deal.<br /></div><div><br
/></div><div>MichaelGould</div><div>Intermodal Software Solutions, LLC</div><div>904-226-0978</div></span> 

pgsql-general by date:

Previous
From: Jasen Betts
Date:
Subject: Re: COPY FROM (query) in plpgsql
Next
From: Sim Zacks
Date:
Subject: Re: Security setup.