Clarification Regarding How The Host Identifier Works (Doc ID 1569656.1)

Last updated on AUGUST 08, 2017

Applies to:

Oracle Access Manager - Version 11.1.1.5.0 and later
Information in this document applies to any platform.

Goal

When creating a new Webgate (11g), one of the fields to enter is "preferred host". this is user defined, but per the documentation it is recommended to name it the name of the server. Regardless, this automatically creates a 'host identifier' with the name of the preferred host.

How does the host identifier really work?  If one were to take the output files the webgate creates (ObAccessClient.xml and cwallet.sso) and copy it to the Web Tier, and complete the policy configuration, everything works as expected.

How does the webgate and access manager knows to intercept the request?  Looking at the "operations" field of the host identifier that got automatically created, it created a value which matches the host identifier name. However, it does not contain the port number the Web Tier is running on (port 7777).  Instead, the port number field is blank, yet everything is working properly.

How is the host identifier working if in the operation field whereas it doesn't actually have the proper servername and port combination which actually matches the web tier? It seems to be doing it dynamically somehow. Please provide clarification on exactly how this happens.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms