SSOGEN / Oracle Access Manager vs SSOGEN: What Each Product Documents
Compare
Oracle Access Manager vs SSOGEN: What Each Product Documents
Oracle Access Manager vs SSOGEN for EBS and PeopleSoft comes down to the integration path: Oracle documents OAM with a directory, or Identity Cloud Service, for EBS single sign-on, while SSOGEN uses its Web Agent in Apache or Oracle HTTP Server with its own identity provider or yours.
Oracle Access Manager vs SSOGEN is a choice between two ways to put sign-in in front of Oracle E-Business Suite and PeopleSoft. Oracle documents OAM (Oracle Access Manager) with a WebGate and an Oracle directory or identity service. SSOGEN needs one Web Agent in Apache or Oracle HTTP Server, with SSOGEN or your own SAML or OpenID Connect provider signing people in.
The table sets out what each vendor documents, row by row, with the Oracle source and the date we read it. This page does not rank the products and says nothing about price or quality.
For a step-by-step migration plan, read the Oracle Access Manager alternative page.
Oracle’s statements come from its own documentation, read on 2026-10-09.
The two guides cover different releases (EBS 12.2 and WebGate 14.1.2), so do not treat them as one design: the Oracle E-Business Suite 12.2 Security Guide and the Oracle HTTP Server WebGate installation guide.
Capability table
Last compared 2026-10-09. Vendors change their products, so check the sources. “Not stated on the pages read” means just that. It does not mean the capability is missing.
| Capability | Oracle Access Manager (Oracle documentation, read 2026-10-09) | SSOGEN (own documentation) |
|---|---|---|
| Documented EBS single sign-on options | Two integration options: Oracle Access Manager with Oracle Internet Directory or Oracle Unified Directory, and Oracle Identity Cloud Service (EBS 12.2 Security Guide). | EBS single sign-on with SAML, with no Oracle Access Manager, Oracle Identity Cloud Service or Oracle Internet Directory to run (Oracle EBS SSO). The integration is an Oracle Validated Integration for E-Business Suite 12.2. |
| Third-party sign-in | Oracle’s guide says: “If a third-party authentication mechanism is used, Oracle Access Manager with Oracle Internet Directory or Oracle Unified Directory or Oracle Identity Cloud Service is still required: they provide bridge functionality between Oracle E-Business Suite and the third-party single sign-on solution.” It also says: “Direct integration with third-party authentication systems and third-party directory services is not supported.” | SSOGEN is a complete identity provider, or signs people in through your SAML or OpenID Connect provider. Confirm with Oracle what this means for your support position. |
| Request interception | “Oracle HTTP Server WebGate is a Web server plug-in that intercepts HTTP requests and forwards them to an existing Oracle Access Manager instance for authentication and authorization” (WebGate guide). | The Web Agent, an Apache module for Apache 2.4, 2.2 and Oracle HTTP Server. In its default mode (SSOGENMode ssogen) it signs the person in through SSOGEN before the application sees the request. |
| Directory or identity service | Integrated with Oracle Internet Directory or Oracle Unified Directory, or Oracle Identity Cloud Service (EBS 12.2 Security Guide). | SSOGEN’s own users, or the directory behind your SAML or OpenID Connect provider, such as Entra ID, Okta, Ping Identity, AD FS or Active Directory. |
| User name passed to the app | Not stated on the pages read. | In that default mode, the Web Agent sends the name in capitals, in the form EBS and PeopleSoft already read, together with the legacy Oracle single sign-on values those applications expect. The Test action in the console lists every value for a real person before cutover. |
| Linking the SSO user to the EBS user | Not stated on the pages read. | EBS profile options for external single sign-on, such as Applications SSO Type and Applications SSO Auto Link User. Which values apply depends on your EBS release. |
| PeopleSoft | Not stated on the pages read. | PeopleSoft SSO: the Web Agent runs in the Apache or Oracle HTTP Server in front of PeopleSoft and sends the user name in the header PeopleSoft’s sign-on reads. |
Two paths to the same application
Oracle’s design. A WebGate in the web tier catches requests and hands them to an OAM instance.
Oracle identity data. EBS gets identity data from that instance through Oracle Internet Directory, Oracle Unified Directory or Identity Cloud Service. The table quotes Oracle on third-party authentication.
SSOGEN’s design. SSOGEN puts one agent, the Web Agent, in the same web tier. It runs in two modes.
Default mode. SSOGEN signs the person in, either itself or through your SAML or OpenID Connect provider. The agent then passes the user name to the application in request headers, as the header rows in the table describe.
Standalone mode. The same module can also act as a SAML service provider or OpenID Connect client straight against another identity provider, with no SSOGEN server in the path. That mode needs a license key from SSOGEN.
Installer tip. An EBS instance that once had an OAM, OSSO or OID registration returns an error while that registration is still there. Run the cleanup step first.
The Oracle EBS SSO page has the commands, profile options and errors.
What SSOGEN also offers
Beyond the Web Agent, SSOGEN gives EBS and PeopleSoft a complete identity provider:
- Sign-in policies. Policies, assignments and step-up.
- App Proxy. The Gateway App Proxy, for a private web application where nothing is installed next to it.
- One policy and audit log. The same policy, MFA and audit log for EBS, PeopleSoft and non-Oracle applications.
- Agent identity. Agent identity for AI agents.
- Break-glass. A local login path for break-glass accounts, with steps in the Oracle EBS SSO guide.
Where Oracle Access Manager fits
- OAM already in place. You run OAM with Oracle Internet Directory or Oracle Unified Directory, and other applications use it.
- Oracle’s documented path. Your Oracle support deal, audit or contract requires it. Oracle’s guide states the bridge requirement quoted above, so ask Oracle how it applies to you.
- Other Oracle products. They depend on OAM, and you want one access manager for all of them.
- A planned 14c upgrade. You prefer to stay on OAM and move to 14c; OAM 12c end of support sets out the dates and the upgrade steps.
SSOGEN’s single sign-on integration with E-Business Suite 12.2 is an Oracle Validated Integration (Oracle datasheet, 2022). SSOGEN supports its EBS and PeopleSoft integrations directly.
When SSOGEN fits
- Your identity provider. You want it in charge and no separate Oracle directory to run.
- One approach. One approach across EBS, PeopleSoft and non-Oracle applications.
- No OAM, OID or OUD. You would rather not run them, or you do not have them.
- Your existing provider. EBS users sign in through the provider you already run, such as Entra ID, Okta or Ping Identity.
- Agents. AI agents need an owned identity and per-tool permissions (see AI agent identity).
The migration plan on the alternative page keeps OAM in production while you test one application on a clone.
For connection choices, see how to choose a connection method, and for a wider view read single sign-on software.
Questions people ask
Do I need Oracle Access Manager for EBS single sign-on?
Oracle’s 12.2 guide lists OAM with a directory, or Identity Cloud Service, as the documented options. SSOGEN delivers EBS single sign-on without either. Check how that fits your Oracle support deal.
How does a move from OAM to SSOGEN work?
One application at a time. Other applications stay on OAM while you test one on a clone. Clear the old registration on an EBS instance before you turn on the new one.
What replaces a WebGate?
The Web Agent. It runs in the web server and signs the person in before the application sees the request. The table shows the policy and header details.
Sources, all read 2026-10-09: Oracle E-Business Suite 12.2 Security Guide; Configuring Oracle HTTP Server WebGate for Oracle Access Manager (14.1.2).
About this comparison. SSOGEN Corporation prepared this page from Oracle Corporation’s public documentation and web pages, last read on 2026-10-09.
We took care to be accurate, but products, plans and prices change, and we may have misread or missed something, so some statements may be wrong or out of date. This page is for general information only and comes without any warranty.
SSOGEN is not responsible for errors, omissions or decisions made from it. Check the vendor’s own pages and test the products yourself before you decide. If you see a mistake, tell us and we will correct it.
Oracle, Oracle Access Manager, Oracle E-Business Suite, PeopleSoft, Oracle HTTP Server, WebGate, Oracle Internet Directory, Oracle Unified Directory, Oracle Identity Cloud Service, Microsoft Entra ID, Active Directory, AD FS, Okta, Ping Identity and Apache are trademarks of their respective owners.
SSOGEN is an Oracle partner, but Oracle has not reviewed or endorsed this page. Except for Oracle, the owners named are not affiliated with, endorsed by or sponsored by SSOGEN.