pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Gary Stainburn <gary.stainburn@ringways.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: RFC - multi database/application user authentification
Date: Thu, 4 May 2006 13:21:20 -0500
Message-ID: <20060504182120.GQ97354@pervasive.com> (raw)
In-Reply-To: <200605041101.17087.gary.stainburn@ringways.co.uk>
References: <200605041101.17087.gary.stainburn@ringways.co.uk>

I think a better question to be asking yourself is: why are you using
seperate databases for all of this? It certainly sounds like all the
activities are related, so ISTM it would make a lot more sense to put
everything in one database and possibly use schemas to seperate things
logically.

On Thu, May 04, 2006 at 11:01:16AM +0100, Gary Stainburn wrote:
> I have two separate database applications running, one for the initial 
> Pre-Delivery preparation of new vehicles, and one for the final taxing and 
> delivery to customers.
> 
> These two systems were developed independently but are used by the same 
> people.  Each of these databases has a user table, used for initial 
> authentication, and also for logging purposes, i.e. who did what action and 
> when.  Each user table has as it's primary key an int4, but these don't match 
> between the two systems.
> 
> I am about to develop a new system to encompass the whole order to delivery 
> process which will mean the creation of a third system with a third database, 
> user table and authentication process.
> 
> What is the best way to develop an authentication method where one 
> user-id/password system can be used by three separate databases?
> 
> Is it possible to get postgresql to do this cross-database  access or will I 
> have to handle it in the PHP code?
> -- 
> Gary Stainburn
>  
> This email does not contain private or confidential material as it
> may be snooped on by interested government parties for unknown
> and undisclosed purposes - Regulation of Investigatory Powers Act, 2000     
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (3+ messages)  latest in thread

Message-ID: <20060504182120.GQ97354@pervasive.com>
Permalink:  ../20060504182120.GQ97354@pervasive.com/
Also on:    postgresql.org/message-id/20060504182120.GQ97354@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, gary.stainburn@ringways.co.uk
  Subject: Re: RFC - multi database/application user authentification
  In-Reply-To: <20060504182120.GQ97354@pervasive.com>
  References: <200605041101.17087.gary.stainburn@ringways.co.uk> <20060504182120.GQ97354@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox