Oracle Access Manager (OAM) How To Set The WebGate Communication Mode To The Legacy Back Channel Protocols OAP Over TCP At Registration Time
(Doc ID 2732088.1)
Last updated on NOVEMBER 30, 2020
Applies to:Oracle Access Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
There is a new feature and is the Default setting for WebGate to OAM server communication. Whenever an SSO agent is registered(OAM Console or RREG), the following additional parameters are set, by default.
There will be some cases where this new communication mode will not want to be used. To change the communication mode from the default of OAMServerCommunicationMode=HTTP/HTTPS to the Legacy back channel protocols by manually updating the ObAccessClient.xml fike and removing the line that states "OAMServerCommunicationMode=/HTTPHTTPS as described in Doc ID 2647757.1.
- Use oamreg.sh to create the SSO Agents
- To use the Legacy Back channel protocols requires manually to remove the "OAMServerCommunicationMode=HTTP/HTTPS, then there is no point of automation perspective of oamreg.sh script to automatically generate SSO Agent
How To Set The WebGate Communication Mode To The Legacy Back Channel Protocols OAP Over TCP At Registration Time?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document