Re: Using verify_function once it has been initialized

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Thu, 19 Dec 2002 16:05:22 -0000
Message-ID: <atsqom$op8$1$8302bc10@news.demon.co.uk>

As far as I know, the only simple method for changing passwords when a verify_function has been attached is to use the PASSWORD command from within SQL*Plus.

As you will have seen, the verify_function has to have the old and new passwords as inputs - and NOTHING knows the actual value of the old password, so it has to be supplied by the user in response to a prompt.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Coming soon a new one-day tutorial:
Cost Based Optimisation
(see http://www.jlcomp.demon.co.uk/tutorial.html )

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____England______January 21/23


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html





Karen Byrd wrote in message
<9ca71242.0212190747.159c85ac_at_posting.google.com>...


>After initializing verify_function to set up password complexity

rules,


>users can't change their own passwords. Passwords can only be changed

>from SYSTEM(or SYS). Yes, the function does have EXECUTE privilege

granted


>to the PUBLIC.

>

>What needs to be done in order to allow users to change their own

>passwords?

Received on Thu Dec 19 2002 - 10:05:22 CST