Oracle Access Manager 11g R2PS2 (OAM 184.108.40.206) and Siteminder Integration: How to use DCC instead of ECC WebGate topology?
(Doc ID 2332757.1)
Last updated on OCTOBER 17, 2019
Applies to:Oracle Access Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
On OAM 18.104.22.168.171017, have followed Article Integrating SiteMinder SSO with Oracle Access Manager 11g (<Note:1670077.1>) in order to integrate Siteminder and OAM 22.214.171.124 using Header based Identity propagation Approach with the embed credential collector as mentioned in 2.1.1 of this article. It works perfectly.
What are the steps we must take for this integration if we use the DCC. What are the end points that need to be protected when using DCC?. In other word what are the equivalent 2.1.1 steps if we are using a DCC instead of ECC?.
The above article says you must protect the login endpoints (/oam/server context root), so the question is (/oam/server context root) the login endpoint for the DCC?, thought that was only for ECC, right? Or asked in another way, What is the login endpoint for the DCC?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document