Oracle Access Manager (OAM) Detached Credential Collector (DCC) - Tunneling Causes Application Development Framework (ADF) Based Custom Login Page To Not Render Correctly
(Doc ID 2619326.1)
Last updated on MARCH 28, 2022
Applies to:Oracle Access Manager - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
After enabling DCC tunneling on the WebGate, when accessing the same custom ADF login page that worked prior, it is now not rendering.
DCC WebGate: Ext_OHS_1
Resource WebGate: Ext_OHS_2
WebGate for Internal requests: Int_OHS_A
1. Requests to OHS protected by the resource webgate Ext_OHS_2, use the DCC webgate to authenticate users with a federration IDP. This works fine
2. Requests to internal resources that use Int_OHS_A, also redirect to the DCC webgate, and if the standard LDAPScheme is used to protect the resources in Int_OHS_A app domain, logins also works fine.
3. The problem... Switch from the standard LDAPScheme to a scheme for a custom ADF login application, at the context "/login" the /login resource is not accessible. The DCC tunnel configuration for the custom ADF login application, context does not seem to be working.
- The issue is only seen when using a DCC Webgate and a custom ADF login page
- Applied latest BP18 on the OAM server and BP13 on the Webgates
Steps to Reproduce Summary
- Created ADF custom login page and deployed on weblogic servers
- It is successfully rendered when accessing the adf custom login page using weblogic server host and port
- After enabling DCC tunneling on the webgate, when accessing the same custom login page, it is not rendering
- OAM 11g How to use Detached Credential Collector (DCC) Tunneling for Custom Login Page and Context (Doc ID 2435279.1)
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