Let's walk through an example deployment. An Oracle 10g server is configured for SSO multi-domain; an Authentication WebGate is configured and, in another domain, a Resource WebGate is configured.
In Acess Policy Manager, an AAA OAM server has been configured and includes the details of the OAM Access Server and the two AccessGates. Two virtual servers have been configured with OAM native integration enabled.
This figure depicts the traffic flow for the example.
When you create a AAA OAM server, its transport security mode must match the setting in OAM. The procedure for configuring a AAA OAM server with open or simple transport security mode is different from the procedure for configuring a AAA OAM server with cert transport security mode. Only one AAA OAM server is supported and it must be configured following the procedure that is appropriate for the mode.
Before you start to integrate Access Policy Manager with OAM, configure the Access Server and AccessGates through the Oracle Access administrative user interface. Refer to Oracle Access Manager Access Administration Guide for steps.
Follow these steps to integrate Access Policy Manager with OAM 10g server.
An example follows.cp aaa_cert.pem /config/aaa/oam/Common/$OAM_Server_Name/AccessGateName/oblix/config/ cp aaa_chain.pem /config/aaa/oam/Common/$OAM_Server_Name/AccessGateName/oblix/config/ cp aaa_key.pem /config/aaa/oam/Common/$OAM_Server_Name/AccessGateName/oblix/config/ cp password.xml /config/aaa/oam/Common/$OAM_Server_Name/AccessGateName/oblix/config/ cp ObAccessClient.xml /config/aaa/oam/Common/$OAM_Server_Name/AccessGateName/oblix/lib/ When you restart the EAM service, it will detect that the AccessGates are configured in cert mode and that the OAM AccessGate configuration files are present in the local directories. As a result, the EAM service will initialize the AccessGates without running configureAccessgate for the initial bootstrap.