Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 126.96.36.199.5 and later
Information in this document applies to any platform.
OAM upgraded from OAM 11gR2 PS2 BP07 to OAM 11gR2ps3 BP05.
The replication agreement on OAM 11gR2PS2 was created using "weblogic" user (even when OUD was their SystemStore) and with the role mapping changes in the OAM 11gR2PS3, weblogic user could not be used anymore to invoke REST services.
The existing agreement had to be disabled/deleted and recreated using the admin user in the OUD which was configured as SystemStore.
However, when webgate is created on Master DC, the webgate profile in clone DC showed the OAM servers on the master as the primary server list.
Expected behaviour is to have OAM servers on the clone DC listed as Primary Servers in the webgate profile.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms