SAML2 federation fails due to presence of &#13 characters in signature and certificate blocks in AM 6,,, and

Last updated Jan 8, 2019

The purpose of this article is to provide assistance if SAML2 federation fails because the Service Provider (SP) cannot parse the signature or certificate generated by the Identity Provider (IdP) due to the presence of &#13 characters at the end of the lines, when AM is the IdP.

2 readers recommend this article


Federation fails when using SP initiated SSO; the SP may see references such as "Invalid SAML signature" in their logs and will not be able to parse the signature or certificate blocks.

The Federation debug log will show the signature and certificate blocks with &#13 at the end of lines, for example:


Recent Changes

Upgraded to, or installed AM 6,,, or


The xmlsec library used in these versions is 2.1.1, which has a known issue that causes line breaks to be replaced with these characters when the ignorelinebreak property is enabled. This property is enabled using either of the following JVM options:

If the XML parser used by the SP to process the assertion is not permissive, these characters will cause federation to fail. However, if the XML parser is permissive (as used by AM), federation will succeed; this explains why this issue will not affect you if AM is also acting as the SP. 


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

See Also

FAQ: SAML certificate management in AM/OpenAM

SAML Federation in AM/OpenAM

SAML v2.0 Guide

Related Training


Related Issue Tracker IDs

OPENAM-13577 (xmlsec 2.1.1.jar used in AM6 have issues when linebreaks enabled)

Copyright and TrademarksCopyright © 2019 ForgeRock, all rights reserved.