Re: password complexity -- implementing security changes

From: rjamya <rjamya_at_gmail.com>
Date: Fri, 3 Mar 2006 10:14:43 -0500
Message-ID: <9177895d0603030714r47ec655ep508e54e46403c17@mail.gmail.com>

no you are not slow ... there are two things ...

1. users can change their password using our application.
2. if they miss, they can call the data center, which changes their password to a temp one and then user must change on the first logon (alter use xxx identified by yyy password expire).

options 2 is used mostly by those folks who have been on long leave or are mostly on road.

Raj

On 3/3/06, Baumgartel, Paul <paul.baumgartel_at_credit-suisse.com> wrote:
> Raj--
>
> Call me slow, but I'm not following. User password expires, user calls help desk, user gets "temporary" password--what then? Does user keep that password for 60 days or change it using the stored procedure? What about this setup reduces calls to help desk?
>
> Paul Baumgartel
> paul.baumgartel_at_credit-suisse.com
> 212.538.1143

clear as mud??
Raj

---

Got RAC?

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Mar 03 2006 - 09:14:43 CST