Summary
Most time about APPS we don't know how to handle users about password when today companies must apply password change policies.
Question
DESCRIPTION:
As part of as usual business security policies, from time to time ( not too much) IT department requestes to SDM admin team to change passwords all related with history users and repository users.
Even though, there are a couple of KMs related, anyone talks about users from APPS side, so here is the first time that we have that on the table.
Look, next information to have a clear picture how to deal with this APPS implementation and layer.
Answer
-----------------------------------------------------------------------------------------------------------
This process is helpful when you want to change history users and repository users.
1. Ensure the encryption key has not been changed.
The master encryption key is required for verification purposes. You can change the encryption key after completing the steps in this section.
2. Open a command window.
3. Run the password manager utility using the following syntax:
Platform Syntax
UNIX <install_directory>/obt/bin/runPwManager.sh -p
DOS <install_directory>/obt/bin/runPwManager.bat -p
4. Environment user passwords change you can use Nav : Environment à Active Environment à Locations (i.e for the location users OBT_IF, OBT_RELOC etc..)
5. For passwords change on HIST users, once it is created in the History users it is just normal DBA_USER as per as I know. It should not impact anything.
Here a list of as usual history users for you for reference, remember that this list depends on customer modules using it:
|
|
||||
|
XLA
|
||||
|
||||
|
OKC
|
||||
|
ONT
|
||||
|
INV
|
||||
|
APPLSYS
|
||||
|
HR
|
||||
|
PO
|
||||
|
AP
|
||||
|
APPS
|
||||
|
FA
|
||||
|
OE
|
||||
|
AR
|
||||
|
PA
|
||||
|
CN
|
||||
|
GL
|
||||
|
APPS_NE
|
||||
|
OBT_RELOC
|
OBT_REP