Re: [GENERAL] [HACKERS] USER Profiles for PostgreSQL - Mailing list pgsql-hackers

From Melvin Davidson
Subject Re: [GENERAL] [HACKERS] USER Profiles for PostgreSQL
Date
Msg-id CANu8Fiw0sc8HVDHPM_wBjbjimQmdP2JQkDX6b8yOCKuFn2owpg@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] [HACKERS] USER Profiles for PostgreSQL  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers


On Tue, Sep 19, 2017 at 1:28 PM, Stephen Frost <sfrost@snowman.net> wrote:
Tom,

* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> chiru r <chirupg@gmail.com> writes:
> > We are looking  for User profiles in ope source PostgreSQL.
> > For example, If a  user password failed n+ times while login ,the user
> > access has to be blocked few seconds.
> > Please let us know, is there any plan to implement user profiles in feature
> > releases?.
>
> Not particularly.  You can do that sort of thing already via PAM,
> for example.

Ugh, hardly and it's hokey and a huge pain to do, and only works on
platforms that have PAM.

Better is to use an external authentication system (Kerberos, for
example) which can deal with this, but I do think this is also something
we should be considering for core, especially now that we've got a
reasonable password-based authentication method with SCRAM.

Thanks!

Stephen

Perhaps, as an alternative, although not currently supported, connection attempts can be added in the future to "Event Triggers"?
Users could then create a trigger function to enable/disable logins.

--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: [HACKERS] Show backtrace when tap tests fail
Next
From: Andres Freund
Date:
Subject: [HACKERS] Running some tests with different segment sizes