HI Prasad,
What you are seeing is the post preservation page. This is normal behavior for siteminder framework agent. When the SMSESSION needs to be updated and the request happens on a HTTP POST process the agent has to capture the post data so that after then SMSESSION is updated it can retrieve the data and complete the POST process without loosing the data or causing a problem.
Now usually this process happens so quickly that it is not seen by most users. Depending on Load on the policy servers and web servers the time it takes to complete may very so some users may see it some times but not all of the time. But the process does happen any time the SMSESSION needs to be updated and the HTTP request is of method POST.
Is this causing some type of problem for you?
Is the screen not continuing on automatically?
There are a couple of ways this can be disabled. You will need to review in conjunction with your setup to see which is best suited for your needs:
OverlookSessionForMethods
Specifies whether the Web Agent compares the request method of all
HTTP requests against the methods listed in this parameter. If a match
occurs, the Web Agent does not create or update an SMSESSION
cookie. Also, cookie providers (if configured) are not updated for that
request.
Default: No default
************************************************************************************
Disable POST Preservation
If you do not need to use POST preservation, you may disable it with the
following parameter:
PreservePostData
Specifies whether the Web Agent preserves POST data when
redirecting requests. When the user is challenged for advanced
authentication, such as forms or certificate authentication, the post
data is preserved during the authentication phase.
Default: Yes
To disable POST preservation, set the value of the PreservePostData
parameter to no.
************************************************************************************
LegacyCookieProvider
Controls whether a framework agent sends a POST request to a cookie provider. When framework agents send a POST request to a traditional agent that is acting as a cookie provider, the redirected request becomes a GET instead and fails. When set to no, the framework agent sends the POST request to the cookie provider. When set to yes, the framework agent does not send the POST request to the cookie provider.
If you are using central agent configuration, you must add this parameter to your Agent Configuration Object. This parameter already exists in local configuration files.
Default: No (POST requests sent)
Note: This parameter applies to framework agents only.
If you can provide more details ont he problem you are facing and the ACO settings for the web agent we might be able to provide more information if this does not answer your questions.
Hope this helps
Gene