Oracle E-Business Suite with Access Gateway Classic SSO reference architecture
This reference architecture describes the components, flow and version requirements for integrating Oracle E-Business Suite and Access Gateway when configured for EBS Classic SSO.
Topics:
Architecture
Flow
- User signs in.
- Send EBS user identity to Access Gateway.
- Using data store lookup UID using EBS user identity.
- Send USER_ORCLGUID (within header) to Oracle AccessGate.
AccessGate generates and EBS session cookie. - Redirect to EBS with EBS session cookie.
-
EBS validates the cookie and establishes the EBS application session.
Components and requirements
| Component | Description and requirements |
|---|---|
| Okta Access Gateway | All versions of Okta Access Gateway support Oracle E-Business Suite when configured as Access Gateway Classic EBS. |
| Oracle E-Business Suite |
Supported versions:
|
| Okta Access Gateway Data Store | Data store configured within Access Gateway and used to connect Oracle Internet Directory (OID) or Oracle Unified Directory (OUD). Provided with EBS user and returning value used as USER_ORCLGUID. |
|
Okta attributes |
USER_NAME, in email address form. |
|
Header attributes |
Header attributes passed by Access Gateway to the Oracle AccessGate to return EBS cookie session.
|
| External URL | External URL specified by the Public Domain field within Access Gateway. For example: ebs-external.example.com |
| Internal URL | Internal URL and port specified by the Protected Web Resource field within Access Gateway. For example: ebs-internal.example.com:8000 |
|
Oracle AccessGate URL |
URL and port used to access instance of Oracle AccessGate. |
| Oracle OID/OUD URL | URL and port used to access instance of either Oracle Unified Directory or Oracle Internet directory. For example: ebs-oid.example.com:3060 |