Oracle Access Manager needs to be configured with a Host Identifier that matches the host identifier variable that you created when you registered Oracle HTTP Server WebGate with Oracle Access Manager. When you registered your WebGate with the Oracle Access Manager, this step was completed automatically for you.
If a host identifier was not created or was deleted after you created your WebGate, you will need to create a new host identifier.
To create a new host identifier, follow the instructions in section 16.4, Managing Host Identifiers, of the Fusion Middleware Administrator's Guide for Oracle Access Management, which can be found at the following URL:
http://docs.oracle.com/cd/E27559_01/admin.1112/e27239/toc.htm
To confirm that you have a configured Host Identifier:
In the Host Name Validation list, ensure that the name of your host identifier under Host Name matches the host identifier that you setup when you registered your WebGate with Oracle Access Manager.
Note: The host identifier field is a value that replaces hostname:port in requests from the webserver to the Oracle Access Manager. For example, your WebGate has a host identifer set to P6EPPM and you make a request in the browser for a resource, such as http://ohs_<
server_name>:<
port>/
p6. The WebGate makes an IsProtected call to the Oracle Access Manager managed server to determine whether the resource is protected; in this instance, the resource is /p6. The WebGate will pass the resource from itself to OAM as http://
P6EPPM/
p6 — this can be seen in trace mode logs of Oracle Access Manager — and then it will attempt to match a policy created in OAM. As a result of this substitution, redirection to Oracle Access Manager for authentication will occur if the actual <host_name>:<port> of the webserver is not set as the host identifier value.
Related Topics |
Legal Notices
Copyright © 1999, 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Thursday, February 04, 2016