DCC Tunneling is Broken After Applying (BP07) Patch in OAM Server

(Doc ID 2207562.1)

Last updated on NOVEMBER 25, 2016

Applies to:

Oracle Access Manager - Version to [Release 11g]
Information in this document applies to any platform.


Setting up a federated solution in OAM with (BP07) Patch applied and configuring DCC tunneling:

Testing a simple scenario by accessing the metadata page fails and getting a blank page (HTTP/1.1 500 Internal Server Error).
All /oam or /oamfed accesses give the same result (500 response).

In the OAM diagnostics log getting 'java.lang.NullPointerException':
[2016-11-04T16:20:01.630+01:00] [oam_server1] [ERROR] [OAM-04020] [oracle.oam.proxy.oam] [tid: [ACTIVE].ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 005G7gpDaj7CwkApr^WByY0000Ch000004,1:119412] [APP: oam_server#] Exception encountered while processing the request: {0}. Message : {1}[[
at oracle.security.am.proxy.oam.requesthandler.HTTPRequestHandler.process(HTTPRequestHandler.java:218)
at oracle.security.am.proxy.oam.requesthandler.NGProvider.getHttpResponse(NGProvider.java:515)
at oracle.security.am.proxy.oam.requesthandler.NGProvider.getResponse(NGProvider.java:491)


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