|
Security Incident people soft
|
|
|
hi, folks would you mind help me with this, there is DBA in my company that saids is not posible changue password from VP1 account in peoplesoft, because this it could make changues in our operations, and operations can be stopped, is this true? and if not how can I changue it?
in other way dou you know what kind of sw can I use in order to get logs in people, becasuse I detected that this DBA made a couple of accounts with admin privilegies, and then he erased it, so i think that he erase the logs too.
thanks alot for your help and if there is something that i can do for you said it!!
|
|
|
|
|
|
|
Re:Security Incident people soft
|
|
|
I'd say that not only is it possible to change VP1's password, it's best to delete it along with all of the delivered accounts and set up more limited accounts to meet your local security needs. For example, there's no reason you need a superuser account to run your application server or process scheduler, so create a more limited account called PSAPP (or whatever) with just the necessary security.
But I digress. I'm guessing the reason your DBA doesn't want to change the password is that it's used for lots of other stuff like your App Server, Process Scheduler, authenticate XML Link, run external Component Interfaces, etc., and he's not sure what might get missed if the password is reset. So the first step would be to identify everything that's using the VP1 password. Then come up with a plan to change the passwords in all of the config files or external apps that use it. Actually do the password reset in a non-production environment and test everything to make sure you got it all. Finally, schedule some down time so that you can recycle the application after the passwords are changed.
|
|
|
|
|
|
|