Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SAML data pages are cleared after passivation



The content of D_SAMLAssertionDataPage and D_SamlSsoLoginInfo is lost after the requestor passivation. This occurs post upgrading Pega 7.2.2 to Pega 8.2.1 and migration to Pega Cloud.

Error Messages

- Caught exception parsing XML stream org.xml.sax.SAXParseException: Premature end of file. at ~
at at pega.pegarules.integration.engine.internal.mapping.xml.XMLParserBase.parseDocument( ~[printegrint.jar:?] at pega.pegarules.integration.engine.internal.mapping.ParseRuleUtils.invokeXMLParseRule( ~[printegrint.jar:?] at pega.pegarules.integration.engine.internal.util.PRParseUtils.parseXML( ~[printegrint.jar:?] at pegarules.generated.activity.ra_action_pyloadsamlassertion_b2a706cee649f05784b59248b048a498.step1_circum0( ~[?:?]

Steps to Reproduce

  1. Log in with (Single Sign-On) SSO
  2. Verify the data page on the Clipboard
  3. Wait for an hour (confirm that the requestor is passivated via the Admin Studio Requestors listing)
  4. Take a further action in the user's browser which reactivates the requestor
  5. Reverify the Clipboard. The data pages are blank

Root Cause

A defect in Pegasystems’ code or rules.


This issue is addressed in the Pega 8.2.4 patch release.


Suggest Edit

Published December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us