OAM Does Not Take New Host Identifiers Into Effect

(Doc ID 2081480.1)

Last updated on MARCH 08, 2017

Applies to:

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

Goal

You added a number of entries to an OAM Host Identifiers named my-oracle:
my.oracle.us
my.oracle.us:80
my.oracle.us:9081
my.oracle.us.intranet.local
my.oracle.us.intranet.local:80
my.oracle.us.intranet.local:9081

When you try to access these sites, OAM does not accept show they are protected.

Here are the results from the OAM Test Tool:

[9/16/15 1:31 PM][request][connect] yes
[9/16/15 1:31 PM][response] Connected to primary access server
[9/16/15 1:31 PM][info] Importing URI : http://my-oracle/EBS_UI_Web/myMagic
[9/16/15 1:31 PM][info] Parsed scheme : http
[9/16/15 1:31 PM][info] Parsed host : my-oracle
[9/16/15 1:31 PM][info] Parsed port :
[9/16/15 1:31 PM][info] Parsed resource : /EBS_UI_Web/Magic
[9/16/15 1:31 PM][request][validate] no
[9/16/15 1:31 PM][response] Major code: 5(ResrcOpNotProtected) Minor code: 2(NoCode)

You suspect that this may be related to an issue where the OAM server, filled up its disk. However, you have cleared up the disk space but this problem still occurs.

How could you get OAM to process the new host identifiers?

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