> -----Original Message-----
> From: DENNIS WILLIAMS [mailto:DWILLIAMS_at_LIFETOUCH.COM]
>
> I think the real issue is who is going to keep the usernames
> and passwords
> maintained. Is it you? Do you have that much spare time?
At my previous employer, the responsibility of maintaining usernames at the
OS level (for those that needed OS accounts), the network level (e.g.
e-mail) and ALSO the database level was the responsibility of someone in the
systems administration group. We wrote a package for them with interfaces to
add a username with the appropriate role / password, another function to
remove a username, and a third function to change a user's password. If your
company is large enough that adding/removing usernames happens frequently,
then obviously it should not be the task of the DBA.
I realize that some third-party applications are written to depend on a
single username in the database. But how can you force those applications to
use dbms_application_info to generate some client information unique to each
user? For any in-house application I still think that individual usernames
are preferrable.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jacques Kilchoer
INET: Jacques.Kilchoer_at_quest.com
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Wed Jul 31 2002 - 14:59:38 CDT
