OAM 10g: Not Able To Login To OAM After Changing OVD Remote Base (Doc ID 1298238.1)

Last updated on MARCH 08, 2017

Applies to:

COREid Identity - Version: 10.1.4.1 and later   [Release: 10g and later ]
Information in this document applies to any platform.

Symptoms

The purpose of this document is to solve the issue of not able to login to OAM identity console after changing OVD remote base from DC=example,DC=com to OU=Users,DC=example,DC=com .

As well we noticed that after doing this change the OAM Administrator user can login to the access system console but is not able to list the available domain policies.

So the OAM administrator is not considered a valid OAM administrator after doing that change.

Cause

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