> -----Original Message-----
> From: DENNIS WILLIAMS [mailto:[EMAIL PROTECTED]]
>
> 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.
