Re: Oracle Password Aging
Date: 1996/03/13
Message-ID: <4i7221$6lp_at_phoenix.michsb.trw.com>#1/1
In article <313B2B5D.167EB0E7_at_bms.com>, Joe Kazimierczyk <kaz_at_bms.com> writes:
> Dave Erwin wrote:
> >
> > Does anyone know of a good way to do password aging in Oracle.
> > I know you can do it which an externally identified ( OPS$)
> > ...
>
> We use a product called SQL<>Secure from Braintree Technologies.
> One of it's features is tracking the last password change time.
> Let me know if you want more info, or call them at 617-982-0200.
>
> _________________
> Joe Kazimierczyk
> kaz_at_bms.com
The way I'm going about it is as follows: We have a table (let's call it 'users') where we store various info about all our application users (last name, first name, manager, etc). I added a field to this table called 'pswd_chng_date' to store the date of the last password change for each user. In our main form that all users initially enter, I added a trigger that executes when the form is entered. This trigger compares sysdate with the date in the users.pswd_chng_date field for the current user. If the difference is greater than x number of days, the trigger invokes a "password change" form in which the user enters his/her old password, followed by a new password, followed by a verification. The password is then actually changed by issuing a 'Forms_DDL' built-in which executes an 'alter user' command. Then the users.pswd_chng_date field is updated to the value of sysdate.
Roger Hale
rhale_at_michsb.trw.com
Received on Wed Mar 13 1996 - 00:00:00 CET