OAM11gR2:Parsing Error When Importing OAM IDP Metadata

(Doc ID 1927566.1)

Last updated on JUNE 06, 2017

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


Customer has OAM configured as IDP and WLS 10.3.6 as SP.

There is a known issue with the metadata exported from OAM Admin Console. It's discussed in detail in the below note :

Metadata From OAM User Interface May be Considered Invalid by Some Federation Solutions (Doc ID 1664839.1)

Hence, metadata generated at http://OAM_managed_server_host:port/oamfed/idp/metadata is being used.

Importing this metadata at WLS causes parsing error. WLS logs report the below exception :

<Sep 10, 2014 7:23:37 AM EDT> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.management.utils.CreateException: Unable to parse XML
    at com.bea.security.saml2.providers.SAML2SecurityHelper.consumeIdPPartnerMetadata(SAML2SecurityHelper.java:621)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
Caused by: org.opensaml.xml.parse.XMLParserException: Unable to parse XML
    at org.opensaml.xml.parse.ParserPool.parse(ParserPool.java:151)
    at org.opensaml.common.xml.ParserPoolManager.parse(ParserPoolManager.java:139)
Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 12363; cvc-elt.4.2: Cannot resolve 'query:AttributeQueryDescriptorType' to a type definition for element 'md:RoleDescriptor'.
    at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
    at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
    at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:437)
    at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
    at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325)



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