How To Configure OAM Federation In Separate Domain To Serve As Standby/Disaster Recovery SP
Last updated on JULY 13, 2018
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
- Two OAM domains, Production (Domain A) and DR (Domain B).
- OAM in Domain A serves as an SP in an IdP-initiated transient SAML 2.0 identity federation.
- OAM in Domain B serves as DR
Need it to contain the same federation identity (certificates, metadata, etc) as in Domain A so if we switch traffic to DR, the IdP will federate with DR transparently without any additional configuration on the IdP.
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