From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: rolcanlogin vs. the flat password file |
Date: | 2007-10-17 16:47:26 |
Message-ID: | 47163C9E.3000207@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander wrote:
> On Wed, Oct 17, 2007 at 05:09:25PM +0100, Dave Page wrote:
>> Stephen Frost wrote:
>>> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>>>> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>>>>> There's legitimate use for creating a role with NOLOGIN and a password.
>>>> If we think that, then we shouldn't have a message at all.
>>> I'm not sure I agree with that. I don't agree that there's really a
>>> legitimate use for creating a role w/ NOLOGIN and a password either, for
>>> that matter.
>> Preparing a new user account prior to an employee starting? In my last
>> post we would do that regularly - setup all the accounts etc for the new
>> user, but disable them all until the start date.
>
> Yeah, but did you actually set a password for them?
Yeah, then have them change them all during day 1 IT induction training.
We had a much smaller team that I know you do, and the staff that would
do the account setup would often be busy first thing on Monday morning
when new starters might often arrive - so we would just 'flip the
switch' on the pre-configured accounts.
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-17 16:58:53 | Re: Why copy_relation_data only use wal whenWALarchivingis enabled |
Previous Message | Magnus Hagander | 2007-10-17 16:41:00 | Re: rolcanlogin vs. the flat password file |