My Oracle Support Banner

<Jazn-Web-App Auth-Method="CUSTOM"> In Orion-Web.xml returns error: clsName=CUSTOM not found (Doc ID 860391.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Containers for J2EE - Version to [Release AS10gR3]
Information in this document applies to any platform.
This problem can occur on any platform.


When implementing a  "Plug-gable Identity Management Framework" (PIMF). 
Chapter 13. Oracle® Containers for J2EE Security Guide.

The documentation states that:

"The <jazn-web-app> element is also supported in the orion-web.xml file, as a sub-element of
<orion-web-app>, for a particular Web application. A setting there overrides the
orion-application.xml setting for that Web application."

<?xml version = '1.0' encoding = 'windows-1252'?>
<orion-web-app ... schema-major-version="10" schema-minor-version="0"
<jazn-web-app auth-method="CUSTOM_AUTH"/>
<security-role-mapping name="SecureRole">

However when the <jazn-web-app auth-method="CUSTOM"> entry is used in orion-web.xml, it
generates an error "Missing class: CUSTOM". 

deployment.url = file:/C:/SOFTDEV/DAF/SSODESCRIPTOR/SSODESCRIPTOR-oc4j-app.xml, realm.default =, provider.type = XML }] clsName=CUSTOM  
  16:21:44 clsLdrDebug
FINER: clsNames[0]=CUSTOM
  16:21:44 clsLdrDebug
FINER: clsLdr.parent=default.root:0.0.0
  16:21:44 clsLdrDebug
FINER: clsName=CUSTOM not found:

Missing class: CUSTOM




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.