On Fri, Mar 8, 2013 at 4:07 AM, Albe Laurenz wrote:
> Victor Yegorov wrote:
> > 2013/3/8 Albe Laurenz
> >> This way you can also force a certain password expiry date
> >> (PostgreSQL does not have a password life time).
> >
> > What bout ALTER ROLE ... VALID UNTIL 'timestamp' ?
>
> That's the pas
Victor Yegorov wrote:
> 2013/3/8 Albe Laurenz
>> This way you can also force a certain password expiry date
>> (PostgreSQL does not have a password life time).
>
> What bout ALTER ROLE ... VALID UNTIL 'timestamp' ?
That's the password expiry date.
Oracle's concept is different: it sets a limit
2013/3/8 Albe Laurenz
> This way you can also force a certain password expiry date
> (PostgreSQL does not have a password life time).
>
What bout ALTER ROLE ... VALID UNTIL 'timestamp' ?
--
Victor Y. Yegorov
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 a
On 03/07/2013 03:10 AM, MURAT KOÇ wrote:
Hi list,
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 bef
Hi list,
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_T
