There are different ways of integrating applications with OAM. The following are the high level integration patterns. Most of the Identity Management products (Forgerock Access Manager) provides similar integration patterns.
The following are the different integration patterns used by different clients with the experience i have so far.
Webgate Integration
This integration deploys anOracle Access Manager WebGate plugin on the clients Webserver like Apache 2..4, IHS or IIS.
When an application doesn’t support technologies like SAML v2.0 or OAuth or OIDC or clients cannot change the application to support APIs for authentication and session management, then the suitable option is to use the Webgate.
This requires the client application hosting the resources to install a compatible Webgate plugin on a webserver and configuring the Webgate files to talk to the Oracle Access Manager, the policy decision point. This could require opening of firewall to port 5575 to the servers hosting OAM. This port is the communicating channel for the WGs running on the clients webserver.
This is very similar to the web agent or the J2EE agent protecting an web application using ForgeRock OpenAM.
Integration WebGate Farm
In this model of integration with OAM, the client doesn’t have to install a Webgate Plugin, instead the Identity management team that…
