marie_randall
Member
I wish to make our JDE Oracle data base more secure and am seeking guidance
on how to do that.
Our stats:
1. We are running OneWorld B733, SP11.1 on Sun Solaris UNIX.
2. We are using Oracle 8.1.6.
The JDE installation scripts (e.g., crusrs.unx) established various userids
(e.g., produser) with easy-to-discern passwords and granted all privileges
on every table to Public. That level of security is too loose for our shop.
I have found one Knowledge Garden document (oti-00-0115.htm) that addresses
the issue of securing Oracle objects, but it is incomplete from my
perspective. I have additional questions:
1. The abovementioned document lists three userids (jde, jdedba, produser)
as needing full privileges but then suggests that there may be others that
need similar treatment. What are the other critical userids used internally
by JDE apps?
2. We want to change the passwords for key Oracle userids (jde, etc.). What
do we need to do to keep JDE apps (e.g., P01012) functioning if we change
passwords associated with these userids?
on how to do that.
Our stats:
1. We are running OneWorld B733, SP11.1 on Sun Solaris UNIX.
2. We are using Oracle 8.1.6.
The JDE installation scripts (e.g., crusrs.unx) established various userids
(e.g., produser) with easy-to-discern passwords and granted all privileges
on every table to Public. That level of security is too loose for our shop.
I have found one Knowledge Garden document (oti-00-0115.htm) that addresses
the issue of securing Oracle objects, but it is incomplete from my
perspective. I have additional questions:
1. The abovementioned document lists three userids (jde, jdedba, produser)
as needing full privileges but then suggests that there may be others that
need similar treatment. What are the other critical userids used internally
by JDE apps?
2. We want to change the passwords for key Oracle userids (jde, etc.). What
do we need to do to keep JDE apps (e.g., P01012) functioning if we change
passwords associated with these userids?