Introduction

This is the third part in a 6-part series of blogs. The topic that will be covered is WebGate installation, configuration and registration. It will focus on the Oracle Access Manager (OAM) 12.2.1.4.0 version of the Access server and its certified and supported components.

WebGate Installation and Configuration

The installation and configuration of the OAM 12.2.1.4.0 WebGates are covered in the Middleware, Fusion Middleware, Release 12.2.1.4, Installing WebGates for Oracle Access Manager.

The installation and configuration of the OAM 12.2.1.4.0 Webgates are covered in the Middleware, Fussion Middleware, Release 12.2.1.4.0, Installing WebGate for Oracle Access Manger documentation.

High Level

  • Installation – Installs the WebGate binaries into the applicable Web Server location.

Note There is no download or installation required for the OHS WebGate module, as it is part of the OHS install. For more information on the OHS 12.2.1.4.0 WebGate refer to “Getting To Know The Oracle HTTP Server 12c (OHS 12.2.1.4.0) WebGate (WG) (Doc ID 2701267.1)”

  • Configuration – No GUI interface. Via command line tools manually run two scripts:
    deployWebGateInstance” Copying files from WebGate Oracle Home to WebGate Instancedir
    EditHttpConf” – Copies the appropriate _WebGate.template file and new WebGate.conf file to the defined location. It Updates the Web Server configuration file so it includes the WebGate.conf and generates a WebGate configuration file.

WebGate/Agent Registration

Registering WebGates (and the programmatic equivalent, Access Clients) can be accomplished by using either the Oracle Access Management Console or the remote registration command-line utility. During registration, you can identify specific applications to be protected by Access Manager policies.

The following topics describe how to register and manage OAM Agents:

For more detailed information refer to “Middleware, Identity Management (IdM), Access Manager, Release 12.2.1.4, Administering Oracle Access Management, 15 Registering and Managing OAM Agents

Wrap up

The OAM WebGate installation is the laying down of its binaries and the configuration is the running of the 2 post installation scripts. To use a WebGate it must be registered in order to know which Identity specific applications it is supposed to protect and what authentication/authorization policies it is supposed to enforce.

Related Articles: