Add an Oracle JD Edwards application

The purpose of this tutorial is to go through the process of setting up an Oracle JD Edwards application with Okta through the Access GatewayAdmin UI.

This application is part of a class of applications which exchange user information using header variables. See Add a generic header application for more information about the Access Gateway generic header application.

Access Gateway also provides a sample header application. See Add a sample header application.

Architecture

JD Edwards Architecture

Flow
  1. User signs in.
  2. Send user identity to Access Gateway.
  3. Rewrite redirect per policy.
  4. Send JDE_SSO_UID, as header field, to Oracle JD Edwards.

  5. JD Edwards application responds to request.
For details see Oracle JD Edwards reference architecture.

Before you begin

  • You have access to the JD Edwards EnterpriseOne Server Manager Management console and can configure Single Sign-On.
  • Backing application is a supported JD Edwards app version:
    • v9 or later
  • Appropriate DNS entries for both the header application and the external exposed new URL exist.
    ValueDescription
    https://jd-edwards-external.example.comExternal legacy application URL.
    https://jd-edwards-internal.example.comProtected application URL.
  • Determine all required header attributes required for authentication.

Typical workflow

Task

Description

Create a containing group
  • Best practice, create an optional group to be assigned to the application.

Enable Single Sign-On in JD Edwards EnterpriseOne console

  • Enable SSO for JD Edwards applications
Create application
  • Create the JD Edwards application and required policy.
Test the application
  • Test the application, possibly using header and policy simulation as required.