From: Donald Fraser <postgres@kiwi-fraser.net>
To: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: WITH SYSID feature dropped
Date: Wed, 21 Dec 2005 16:35:00 -0000
Message-ID: <016a01c6064c$7cd1c040$0264a8c0@demolish1> (raw)
References: <011501c60578$47642e40$0264a8c0@demolish1>
<29845.1135094224@sss.pgh.pa.us>
<012201c60583$4a832080$0264a8c0@demolish1>
<20051220170345.GB11637@surnet.cl>
----- Original Message -----
From: "Alvaro Herrera"
> Donald Fraser wrote:
>
> > We developed and have been using since 7.1, and currently running 7.4,
> > bespoke client / database software. The ability to manage users and
security
> > was of high priority and we therefore developed a much more elaborate
user
> > definition where by the information about users was held in our own
tables
> > and we could create a postgresql database user from this table at any
time.
> > To simplify things we controlled the SYSID and used this as the key for
> > mapping a postgresql user to a user defined in our table.
>
> Why not do it the other way around? Create the Postgres user first,
> grab its Oid, then use that as primary key in your user table.
Read my previous posting to answer that one.
The bottom line is there are several solutions to work around our problem:
1) Add a new column to our table that will hold the OID of a postgresql
user.
2) Use the postgresql user name to map to a record in our table (the easy
solution).
I was really just asking, in the first instance, why the changes had taken
place - I appreciate everyones thoughts and inputs for help on our problem.
> On the other hand, it's possible that the new role management in 8.1,
> which has brought much more elaborate privilege handling, could have
> rendered your user handling unnecessary. Have you considered exploring
> that?
Roles are a great improvement to postgresql, but we also talking security
issues here:
Our module controls things like:
1) how long before a user must change their password (daily, weekly, monthly
etc)
2) password rotation - for example a user cannot use the same password
within the last three changes
3) Password semantics: length of password, dictionary word checks and so
on...
4) Restricting a users rights until they have changed their password (they
cannot use the system until they change the password set by the
administrator)
That should give you an insight into why we created such a module as those
are just some of the things it does...
Thanks again for the input.
Regards,
Donald Fraser
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: postgres@kiwi-fraser.net
Subject: Re: WITH SYSID feature dropped
In-Reply-To: <016a01c6064c$7cd1c040$0264a8c0@demolish1>
References: <011501c60578$47642e40$0264a8c0@demolish1> <29845.1135094224@sss.pgh.pa.us> <012201c60583$4a832080$0264a8c0@demolish1> <20051220170345.GB11637@surnet.cl> <016a01c6064c$7cd1c040$0264a8c0@demolish1>
* 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