1. Security Administration Guide
  2. Sign-In Security Setup

Sign-In Security Setup

This checklist is an overview of the steps that are required to set up sign-in security:

Sign-in Security Setup Step

Description

Determine location of the F98OWSEC table.

Ensure that the F98OWSEC table is located in the system data source on the Enterprise Server, and ensure that the table is mapped to the correct data source through the Object Configuration Manager.

If your system data source resides on the enterprise server, the F980WSEC table should reside in the system data source. However, if the system data source is located on the deployment server (or other servers), the F980WSEC table should be moved to the server map data source for the enterprise server.

If you have more than one logic server, you should use only one as the security server.

Set database security on the F98OWSEC table.

From within the DBMS, place database security on this table to prevent a user from accessing the object, except to enter passwords through User Password Revisions.

Place security on the logic server's jde.ini file.

The DBMS user ID and password to the Sign On Security table are stored in this file.

Caution: Implementing jde.ini file security will prevent Server Manager from modifying configuration settings.

Create security records for individual users.

Assign these:

  • Data source

  • System user

  • System password

  • EnterpriseOne password

  • User Status

  • Allowed number of invalid sign-on attempts (optional)

  • Change frequency (optional)

    Note: If you intend to use a unified logon, every user in the EnterpriseOne security database requires a unique user ID (prior to release 9.2.2 only).

Verify and modify the jde.ini file on the JD Edwards EnterpriseOne logic server for the platform environment.

If you use a unified logon (prior to release 9.2.2 only), you need to change the settings for a unified logon in the [SECURITY] section as well as in the EnterpriseOne [SECURITY] settings.

Set up a unified logon server (prior to release 9.2.2 only).

If you use a unified logon with the JD Edwards EnterpriseOne security, set up a unified logon server for each instance of EnterpriseOne on each server. For example, if you have an NT server with multiple releases of EnterpriseOne, you need a unified logon server for each release on the server.

The unified logon server differentiates instances of EnterpriseOne based on the port numbers for these instances. For example, if the port number for EnterpriseOne is 6104, the port number for the associated unified logon server is 6104. Other instances and unified logon servers use different port numbers.

Verify and modify jde.ini file.

Verify and modify the jde.ini file that will be deployed to the server's workstation installations.

Set up sign-in security.

Require sign-in security for all machines.