Oracle JD Edwards reference architecture

This reference architecture describes the components, flow and version requirements for integrating Oracle JD Edwards and Access Gateway.

Topics:

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.

Components and requirements

Component Description and requirements
Okta Access Gateway All versions of Okta Access Gateway support Oracle JD Edwards
Oracle JD Edwards EnterpriseOne.

Supported versions:

  • v9 or later

Okta attributes

logon in the form of an email address.

Header attributes

Header attributes passed by Access Gateway to the Oracle JD Edwards application:

  • JDE_SSO_UID

Policy

Advanced policy required redirect.
For example: proxy_redirect http://jde-internal.example.com:7005 https://$host:$server_port;

External URL External URL specified by the Public Domain field within Access Gateway.
For example: https://jdedwards-external.example.com
Internal URL Internal URL and port specified by the Protected Web Resource field within Access Gateway.
For example: jdedwards-internal.example.com:7005