| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> | 
|---|---|
| To: | MURAT KOÇ *EXTERN* <m(dot)koc21(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> | 
| Subject: | Re: Password Security Standarts on PostgreSQL | 
| Date: | 2013-03-08 10:18:24 | 
| Message-ID: | A737B7A37273E048B164557ADEF4A58B057BB935@ntex2010a.host.magwien.gv.at | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
MURAT KOÇ wrote:
> In Oracle, it could be created a user profile called "PROFILE" and this profile could have below
> specifications:
> 
> PASSWORD_LIFE_TIME     (that describes when password will expire)
> FAILED_LOGIN_ATTEMPTS (specifies number of failed login attempts before locking user account)
> PASSWORD_LOCK_TIME   (specified time after user account is locked because of failed login attempts
> exceeded)
> PASSWORD_VERIFY_FUNCTION  (this allows setting a strong password verify function - min characters,
> password complexity)
> 
> Has PostgreSQL got any capability like this except LDAP, kerberos or PAM authentication ?
There's the "passwordcheck" contrib:
http://www.postgresql.org/docs/current/static/passwordcheck.html
It does the same thing as Oracle's PASSWORD_VERIFY_FUNCTION.
You can write your own password checking function.
This way you can also force a certain password expiry date
(PostgreSQL does not have a password life time).
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Victor Yegorov | 2013-03-08 11:20:37 | Re: Password Security Standarts on PostgreSQL | 
| Previous Message | Sandeep Thakkar | 2013-03-08 06:41:28 | Re: EDB installer should check for valid %COMSPEC% |