Web Agent showing post preservation data error page
search cancel

Web Agent showing post preservation data error page

book

Article ID: 227573

calendar_today

Updated On:

Products

CA Single Sign On Federation (SiteMinder) CA Single Sign On Agents (SiteMinder) SITEMINDER

Issue/Introduction

When running a Web Agent, the browser shows the message on Post Preservation action:

  "This page is used to hold your data while you are being authorized for your request.
   You will be forwarded to continue the authorization process.
   If this does not happen automatically, please click the continue button below."
  1. How to stop this message?
  2. How to edit this message and modify it with another useful message?
  3. Under what circumstances do we get this message?
  4. Why isn't that a known issue?
  5. What are the most common reasons for such messages?

Resolution

Overall, this page doesn't mean an error message.

It's an informative message.

This message is related to the Postpreservation Web Agent feature.

  1. PostPreservation can be disabled by "setting PreservePostData=no in the ACO." (1)(2).
  2. The message can be customized (2)(3).
  3. The Post Preservation occurs "When a timeout or other interruption occurs during a POST operation, the POST preservation page is displayed." (2).

    One of these interruptions might be when the Web Agent needs the browser to visit another Web Agent instance for updating the SMSESSION cookie by a Cookie Provider (1).

  4. This page is not seen on each request, but only when there's a need to "maintain the data, Siteminder must invoke PostPreservation, and this will result in the white page being displayed to the user.

    If PostPreservation is disabled, then the data that the user submitted will be lost and the user will need to resubmit the data [...]" (1).

    Note that if the operation goes quite fast, the user might not even see it in the browser, even if the postpreservation occurs (2).

  5. The most common situation where Postpreservation is needed:

    - Interaction between Framework and Traditional Agent (2);
    - Usage of a Cookie Provider (1)(2);
    - Usage of Dynamic Account Linking at the SP as per documentation (4).

Additional Information

Powered by Wolken Software