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
• Flow
• Components and requirements

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.

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