Add an Oracle JD Edwards app

The purpose of this tutorial is to go through the process of setting up an Oracle JD Edwards app with Okta through the Access Gateway Admin UI console.

This app uses header variables to exchange user information. You can use the Access Gateway sample header app. See Add a generic header app and Add a sample header app.

Architecture

JD Edwards Architecture

Flow
  1. The user signs in.
  2. Okta sends the user identity to Access Gateway.
  3. The rewrite is redirected according to the configuration of the policy.
  4. Okta sends JDE_SSO_UID, as a header field, to Oracle JD Edwards.
  5. The JD Edwards app responds to the request.
See Oracle JD Edwards reference architecture.

Before you begin

  • Verify that you have access to the JD Edwards EnterpriseOne Server Manager Management Console and can configure SSO.
  • Verify that the backing app is a supported JD Edwards app version 9 or later.
  • Identify all required header attributes required for authentication.
  • Ensure that appropriate DNS entries for both the header app and the external exposed new URL exist, as in this example:
    ValueDescription
    https://jd-edwards-internal.example.comThe protected app URL (Access Gateway public domain).
    https://jd-edwards-external.example.comThe external legacy app URL.

Typical workflow

Task

Description
Create a containing group

Create an optional group to assign to the app.

Enable SSO in JD Edwards EnterpriseOne Console

Enable SSO for JD Edwards apps.
Create an app

Create the JD Edwards app and the required policy.
Test the app

Test the app using header and policy simulation.