Oracle Access Manager (OAM) Multi Data Center (MDC) Automated Policy Synchronization (APS) Configuration - Authorization Not Working Correctly In The Clone Servers (Doc ID 2167005.1)

Last updated on AUGUST 02, 2024

Applies to:

Symptoms

• Oracle Access Manager 11g R2PS3 (OAM 11.1.2.3)
• OAM: MDC - APS configuration - Authorization not working correctly in the Clone servers
• APS and MDC configurations in place in our environment
• When modifying any authorization policy in existing application domains, which are active and are being accessed by the users, the changes are getting reflected in the Clone servers, but the changes are not activated until we restart the OAM servers
• It looks like the authorization policies are getting cached and the cache does not get invalidated when the resources and authorization policies are updated in the Clone servers. The changes are activated in the Primary server without any issues. It creates a problem for us, since we have to make a lot of changes in our authorization policies and every time we need to take a downtime to restart the OAM servers to get the changes activated in the Clone servers
  
  
• Error

• MDC configuration - When modifying any authorization policy in existing application domains, which are active and are being accessed by the users, the changes are getting reflected in the Clone servers, but the changes are not activated until we restart the OAM servers.
  
  
  

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.