Solutions
Archived

XML Parsing Error when exporting SAML metadata after upgrading to OpenAM 11.0.1

Last updated Jan 5, 2021

The purpose of this article is to provide assistance if you receive an XML Parsing Error when exporting SAML metadata after upgrading to OpenAM 11.0.1.


1 reader recommends this article

Archived

This article has been archived and is no longer maintained by ForgeRock.

Symptoms

An error similar to one of the following is shown when trying to export the SAML metadata URL (for example: http://example.idp.com:18080/openam/saml2/jsp/exportmetadata.jsp):

error on line 10 at column 6: XML declaration allowed only at the start of the document

Or:

XML Parsing Error: XML or text declaration not at start of entity Location: http://example.idp.com:18080/openam/saml2/jsp/exportmetadata.jsp?entityid=idp&realm=idp Line Number 10, Column 1:<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

Recent Changes

Upgraded to OpenAM 11.0.1

Causes

The XML declaration is incorrectly moved to the 10th line when it must exist on the first line. 

Solution

This issue can be resolved by upgrading to OpenAM 11.0.2 or later; you can download this from BackStage.

Alternatively, you can manually removing the first 9 blank lines from the exported xml file or using the patched exportmetadata.jsp file that is attached to the issue: OPENAM-3841 (Export metadata produces XML Parsing Error after upgrade to AM11.0.1).

See Also

OpenAM 11.0.1 Release Notes › OpenAM Fixes, Limitations, & Known Issues › Known Issues

Related Training

N/A

Related Issue Tracker IDs

OPENAM-3841 (Export metadata produces XML Parsing Error after upgrade to AM11.0.1)


Copyright and Trademarks Copyright © 2021 ForgeRock, all rights reserved.