Overview
JD Edwards EnterpriseOne security runs on a logic server in a dedicated internal process. EnterpriseOne uses an encryption algorithm to ensure that applications other than EnterpriseOne cannot access passwords transmitted across the network.You create a security table on the data server that stores information, such as:
- EnterpriseOne User
The user ID used to sign in to JD Edwards EnterpriseOne.
- EnterpriseOne Password
The user's password, which the software validates when the user signs in to JD Edwards EnterpriseOne.
- System User and System Password
The actual user and password used to connect to all database management systems (DBMS). If the JD Edwards EnterpriseOne environment includes more than one DBMS, you can create different system users and passwords for each data source.
- Change Frequency
The frequency of password changes required by the software.
- Last Change
The date that the password was last changed.
You must define a security record for each user either by group or by individual. It is recommended that you map multiple users to the same system user. For example, each user can use the same system user that the software uses to connect the database management systems. By setting up the security in this manner, you can simplify database administration of users and passwords.
You can also set up unified logon (prior to release 9.2.2 only) with EnterpriseOne to simplify sign-in security. When you set up unified logon, EnterpriseOne uses Windows Authentication to verify security. This verification enables sign-in security to use the network logon information that a user supplies when logging on to Windows; EnterpriseOne does not require the user to enter another user ID and password when signing in.