OAM Policies Not Evaluating Correctly after Performing Cloning with T2P Process
Last updated on OCTOBER 02, 2015
Applies to:Oracle Access Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
After cloning an existing working OAM environment using the T2P process, policies are visible in the OAM console on the clone, but the policies do not evaluate correctly. When webgates are configured to use the clone (or the master is shut down), all protected resources return an HTTP 404 Error, as though the resource is unprotected.
Additionally access to the OAM console in the clone directs to the embedded console login page rather than the SSO login page (due to the policy issue)
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