E.16 Deployments with Freshly Installed 10g Webgates

Use the OAM Server's diagnostic features to debug on the OAM Server side. This section includes the following topics:

• Authentication Issues with 10g Webgates

• Logout Issues with 10g Webgates

See Also:

Configuring Centralized Logout for Sessions Involving 11g WebGates

E.16.1 Authentication Issues with 10g Webgates

Use the following methods to troubleshoot authentication issues when you have freshly installed 10g Webgates in your Access Manager deployment.

• Confirm that your request was protected using an http header trace like Internet Explorer HTTP Headers or Firefox Live HTTP Headers

• Confirm that the request is sent to the OAM Server for authentication

  • GET /oam/server/obrareq.cgi?....

  • Host: oam-server:port

E.16.2 Logout Issues with 10g Webgates

Use the following methods to troubleshoot logout issues when you have freshly installed 10g Webgates in your Access Manager deployment.

• Make liberal use of HTTP Header Trace

• Confirm that the specific logout.html was copied to /access/oamsso folder in the 10g Webgate installation directory. If not present, you must create the logout.html as described in "Configuring Centralized Logout for 10g WebGate with 11g OAM Servers".

• Change the 10g Webgate's httpd.conf to remove the following lines:

  <LocationMatch "/oamsso/*">
  Satisfy any
  </LocationMatch>
  

• From the Oracle Access Management Console, confirm that the LogoutUrls parameter (/oamsso/logout.html) is configured for this Webgate