For initial installations of JD Edwards EnterpriseOne, you must setup system user(s) using the Work With System Users (P980001) program to populate the F98OWPU table. You must set up system users before you can add and associate a JD Edwards EnterpriseOne user to a system user using EnterpriseOne Security (P98OWSEC).
Caution:
If you attempt to add a user with the P98OWSEC program before you add the system user through the P980001 program, the system may add an invalid record to the F98OWPU table. You might have to delete the invalid record from F98OWPU using the SQL Query tool.You must perform security setup signed on to JD Edwards EnterpriseOne from a deployed client. If you perform the steps signed on to the deployment server, you will not be updating the correct security tables for your JD Edwards EnterpriseOne system.
This chapter contains the following tasks:
Section 11.2, "Setting up Security Overrides for Package Build"
Section 11.5, "Setting Up JD Edwards EnterpriseOne Single Sign-on"
To set up signon security:
On P980001 [Work With System Users], click Add.
On System User Revisions, complete the following fields:
System User
JDE
Data Source
DEFAULT
Password
Enter a valid password for your installation.
Password Verify
Enter the same password that you entered in the password field.
Click OK.
Click Find to verify the new record was added.
On P98OWSEC [Work With User Security], complete the following field:
User ID \ Role
JDE
Click Find.
Click Add.
On Security Revisions, complete the following fields:
User ID
JDE
Data Source
DEFAULT
System User
JDE
Password
Enter a valid password for your installation.
User Status
Ensure the Enabled radio button is selected.
Allowed password attempts
Enter a value applicable to your installation.
Password change frequency
Enter a value applicable to your installation.
Click OK.
Click Find to verify that the record was added.
The Package Build process creates tables due to the requirement for metadata. Therefore, you must setup up security overrides for any user who will be doing the package build. For example, if you are setting up the user JDE for path code DV910, you would use this procedure:
Add a System User for Central Objects - DV910 for the owner, DV910, with the database password for DV910. (The default database password is DV910.)
Add a security override for JDE for Central Objects - DV910 using System User DV910.
See Also
JD Edwards EnterpriseOne Package Management Guide
Ensure the JDE.INI
on the Enterprise Server has these settings to support signon security:
[SECURITY]
SecurityServer=server_name
User=JDE
Password=JDE
Default Role=*ALL
DefaultEnvironment=PD910
DataSource=System - 910
History=0
After you modify the JDE.INI
on the Enterprise Server, you must restart the JD Edwards EnterpriseOne Services so the settings can take effect.
Caution:
If you have changed the database password for the JDE user, the password you specify on Enterprise Server injde.ini
must be the new password.Locate the JD Edwards EnterpriseOne client JDE.INI
that is deployed from the Deployment Server. Typically the file can be found at the following location:
x:\JDEdwards\E910\OneWorld Client Install\Misc\JDE.INI
where x: is the drive on which JD Edwards EnterpriseOne is installed.
Ensure that JD Edwards EnterpriseOne client JDE.INI
has these settings:
[SECURITY]
SecurityServer=server_name
DataSource=System - 910
DefaultEnvironment=DV910
Default Role=*ALL
Row Security=NO_DEFAULT
You must set up JD Edwards EnterpriseOne Single Signon Security using the procedures described in Chapter 13, Setting Up EnterpriseOne Single Sign-On of the JD Edwards EnterpriseOne Tools Security Administration Guide.
Caution:
Using default settings may expose a potential security risk. Thus, it is highly recommended to overwrite the single sign-on settings using the single sign-on configuration applications discussed in Chapter 13, Setting Up EnterpriseOne Single Sign-On of the JD Edwards EnterpriseOne Tools Security Administration Guide.