Return-Path: Delivered-To: 2-oracle-l@orafaq.com Received: (qmail 22625 invoked from network); 3 Mar 2006 09:16:47 -0600 Received: from freelists-180.iquest.net (HELO turing.freelists.org) (206.53.239.180) by 69.64.49.119 with SMTP; 3 Mar 2006 09:16:43 -0600 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id EDF982B9B1C; Fri, 3 Mar 2006 10:16:38 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09664-03; Fri, 3 Mar 2006 10:16:38 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 6F7F32B9900; Fri, 3 Mar 2006 10:16:38 -0500 (EST) Received: with ECARTIS (v1.0.0; list oracle-l); Fri, 03 Mar 2006 10:16:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 1995F2B98B5 for ; Fri, 3 Mar 2006 10:16:14 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09544-10 for ; Fri, 3 Mar 2006 10:16:14 -0500 (EST) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.181]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id C6AFB2B9A77 for ; Fri, 3 Mar 2006 10:16:13 -0500 (EST) Received: by pproxy.gmail.com with SMTP id i49so305492pyi for ; Fri, 03 Mar 2006 07:16:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BS9ToaizUODHtwTrZi9cOJE7JWTZ8xAuqJkQbxg9pOImjGJeJY8cV1CmhzHwVrHaIfBB1W5Y+3QoVsa+QKEkhEyEyPU+PpMcacO01JeU8sRGOAZh0uPLpcoh9FNY/T7dycl5qXki4GeXIfXErMWDNOx1FSla48exA+awPrgNGTo= Received: by 10.65.197.9 with SMTP id z9mr1437899qbp; Fri, 03 Mar 2006 07:16:13 -0800 (PST) Received: by 10.64.185.16 with HTTP; Fri, 3 Mar 2006 07:16:13 -0800 (PST) Message-ID: <9177895d0603030716u22d7c1ag39bdce49c78c0c87@mail.gmail.com> Date: Fri, 3 Mar 2006 10:16:13 -0500 From: rjamya To: "Potluri, Venu (GTI)" Subject: Re: password complexity -- implementing security changes Cc: wbfergus@usgs.gov, oracle-l@freelists.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by Ecartis Content-Disposition: inline References: X-archive-position: 31867 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: rjamya@gmail.com Precedence: normal Reply-To: rjamya@gmail.com X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net Only problem ... we CANNOT send password in the email .. our email policy prohibits it. Think about users to unknowingly set up rules to forward their emails ... Raj On 3/3/06, Potluri, Venu (GTI) wrote: > You can use the verify_function and create password complexity. In our > environments, we require users to reset passwords every 90 days. The > password needs to have a capital letter, a number, etc. I have created a > utility which will change password and send email to the person that > owns the account automatically. It is simple enough for helpdesk to use > to accomplish password reset or unlock. The user also gets prompts to > change password themselves starting 14 days prior to expiration. All of > this can be accomplished with the verify_function and assigning a custom > profile to the database accounts. Of course, the helpdesk need not get > involved at all if the users can be coddled to change password 14 days > prior to expiration. > ---------------------------------------------- Got RAC? -- http://www.freelists.org/webpage/oracle-l