Oracle E-Business Suite with Access Gateway Rapid 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 Rapid SSO.
Architecture
Flow
- User sign in
- Send EBS user identity
- Verify EBS user (generates Access Gateway EBS session)
- Redirect to EBS with the EBS session cookie
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 Rapid EBS. |
| Oracle E-Business Suite |
Supported versions:
|
| DBC file | Created by the Oracle E-Business Suite owner and made available to the Access Gateway administrator. |
|
EBS service user account |
Account used by Access Gateway to access the Oracle E-Business Suite. In this example: OAGSSOUSER and granted the UMX|APPS_SCHEMA_CONNECT role. |
|
Okta attributes |
USER_NAME or USER_EMAIL, in email address form. |
|
Header attributes |
Header attributes passed by Access Gateway to the Oracle E-Business Suite application:
|
| 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 |
| Web domain | Rapid EBS SSO uses domain cookies to communicate between Access Gateway and the EBS server. The domain used by the protected web resource and the externally facing instance of Access Gateway must share the same domain. In this example the shared domain is example.com. |