You can set up either Oracle HTTP Server WebGate or mod_OSSO as an Agent for Oracle Access Manager (OAM). Setting up an Agent involves the following steps:
Installing and Configuring the Agent (WebGate or mod_osso)
Registering the Agent as a Partner Application
Restarting the WebLogic Managed Servers
Oracle HTTP Server WebGate is a Web server plug-in that is shipped out-of-the-box with Oracle Access Manager. The Oracle HTTP Server WebGate intercepts HTTP requests from users for Web resources and forwards them to the Access Server for authentication and authorization. Oracle HTTP Server WebGate installation packages are found on media and virtual media that is separate from the core components.
To install and configure Oracle HTTP Server WebGate, complete the following steps:
Install Oracle HTTP Server 11g WebGate for Oracle Access Manager, as described in Installing and Configuring Oracle HTTP Server 11g Webgate for OAM.
Complete the post-installation steps and the registration setup, as described in Post-Installation Steps and Getting Started with a New Oracle HTTP Server 11g Webgate Agent for Oracle Access Manager.
For information about registering WebGate as a Partner Application, refer to the "Agent Registration" topic and the "Managing Agents: OAM (WebGate) and OSSO (mod_osso)" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager. Note that the Administration Server must be up and running when you are registering WebGate as a Partner Application.
For information about restarting Managed Servers, see Starting the Stack.
OSSO Agent (mod_osso) is used by Oracle HTTP Server to check for an existing, valid Oracle HTTP Server cookie. If necessary, it redirects to the Oracle Access Manager runtime server to communicate with the directory during authentication. In addition, it decrypts the encrypted user identity populated by the OSSO server and sets the headers with user attributes.
To install mod_osso, complete the following steps:
Install the latest version of Oracle HTTP Server. For information about installing the Web Tier, including Oracle HTTP Server, see Installing and Configuring Oracle HTTP Server 11g (11.1.1.2.0 or 11.1.1.3.0).
After patching your Oracle Web Tier software to the latest version, run the configuration tool to configure Oracle HTTP Server.
On UNIX operating systems:
<Web_Tier_ORACLE_HOME>/bin/config.sh
On Windows operating systems:
<Web_Tier_ORACLE_HOME>\bin\config.bat
For complete instructions, go to "Configuring Your Components" in Oracle Fusion Middleware Installation Guide for Oracle Web Tier.
Note:
After you configure Oracle HTTP Server, a working instance of Oracle HTTP Server is configured in an Instance Home.Copy the mod_osso.conf file from the <ORACLE_INSTANCE>/config/OHS/<OHS_INSTANCE>/disabled directory to the <ORACLE_INSTANCE>/config/OHS/<OHS_INSTANCE>/moduleconf directory.
Register mod_osso as a Partner Application.
For information about registering mod_osso as a Partner Application, refer to the "Agent Registration" topic and the "Managing Agents: OAM (WebGate) and OSSO (mod_osso)" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager. Note that the Administration Server must be up and running when you are registering mod_osso as a Partner Application.
Edit the mod_osso.conf file to update the location of the osso.conf file as follows:
<IfModule osso_module> OssoIpCheck off OssoIdleTimeout off OssoSecureCookies off OssoConfigFile <location of the osso.conf> <Location> require valid-user AuthType Osso </Location></IfModule osso_module>
Restart Oracle HTTP Server by running the restartproc command in Oracle Process Manager and Notification Server (OPMN) or by using Oracle Fusion Middleware Control.
For information about restarting Managed Servers, see Starting the Stack.