--00163630fd53d9b794048382ee21
Content-Type: text/plain; charset=ISO-8859-1

How do I configure postgres to lock a user's account after X failed login
attempts, where X is an arbitrary number.

Also is there a way to limit the number of concurrent connections on a per
account basis?


-Kevin

--00163630fd53d9b794048382ee21
Content-Type: text/html; charset=ISO-8859-1

How do I configure postgres to lock a user's account after X failed login attempts, where X is an arbitrary number.<br><br>Also is there a way to limit the number of concurrent connections on a per account basis?<br><br>
<br>-Kevin<br>

--00163630fd53d9b794048382ee21--

Kevin Crain writes:

> How do I configure postgres to lock a user's account after X failed login
> attempts, where X is an arbitrary number.

Don't think there is a way to do that.
Perhaps using an authentication mechanism that supports that and then using
it to connect to Postgres..
This page may be of interest:
http://www.postgresql.org/docs/current/static/auth-methods.h tml


> Also is there a way to limit the number of concurrent connections on a per
> account basis?

Don't think there is an option for that either.

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

=D0=9D=D0=B0 05.4.2010 23:11, Kevin Crain =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=
=B0:
[...]
> Also is there a way to limit the number of concurrent connections on a =
per
> account basis?

ALTER ROLE <role> CONNECTION LIMIT <number>;

(http://www.postgresql.org/docs/current/static/sql-alterrole .html)



--
Milen A. Radev


--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Francisco Reyes <lists [at] stringsutils.com> writes:
> Kevin Crain writes:
>> How do I configure postgres to lock a user's account after X failed login
>> attempts, where X is an arbitrary number.

> Don't think there is a way to do that.
> Perhaps using an authentication mechanism that supports that and then using
> it to connect to Postgres..

The usual suggestion is to use PAM if you want a customized login
policy.

regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Le 06/04/2010 20:45, Francisco Reyes a =E9crit :
> Kevin Crain writes:
>
>> How do I configure postgres to lock a user's account after X failed
>> login attempts, where X is an arbitrary number.
>
> Don't think there is a way to do that.
> Perhaps using an authentication mechanism that supports that and then
> using it to connect to Postgres..
> This page may be of interest:
> http://www.postgresql.org/docs/current/static/auth-methods.h tml
>

Yeah, an external authentication tool can probably do that. The internal
ones (password, md5, and crypt) won't.

>> Also is there a way to limit the number of concurrent connections on a
>> per account basis?
>
> Don't think there is an option for that either.
>

Sure, there is one:

ALTER ROLE your-user WITH CONNECTION LIMIT x;

See http://www.postgresql.org/docs/8.4/interactive/sql-alterrole .html
for more details.


--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin