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

SSO reauthenication is not working after session timing out



Using PRPC 5.4SP2 and Siteminder to provide Single Sign On (SSO) authentication. The security requirement is to log users off the application after 30 minutes of idle time, there should be no warnings or ways to restore session. How can we do this in PRPC 5.4SP2?

Error Messages


Steps to Reproduce


Root Cause

When using PRPC 5.4SP2 and older style "User" portals there are timeout configuration options on the custom tab. This will be default provide a way to warn the user a timeout is about to occur and also provide a way for the user to extend thier session if acknowledged. 

The requirements dictated that the user should be automatically logged off. To accomplish this the timeout logic needs to be customized. In older style user portals this requires a custom "frameset" html rule and the inclusion of the following scripting:


function framesetscript_restartTimeoutWarningTimer()
     if (window.gTimeoutTime && gTimeoutTime > 0) {
        var nTimeoutWarningTime= gTimeoutTime  * 60000;

        if (nTimeoutWarningTime >= 0) {
            if (DesktopUserSessionInfo_gRedirectOnTimeout) {
                gTimeoutWarningCountdown = self.setTimeout("framesetscript_showTimeoutLogoffDialog('"+gTimeoutWarningWindow+"')",nTimeoutWarningTime);
            else {
                gTimeoutWarningCountdown= self.setTimeout("framesetscript_showTimeoutWarningLogoff()", nTimeoutWarningTime);
function framesetscript_showTimeoutWarningLogoff()


The function 
framesetscript_restartTimeoutWarningTimer is originally defined in framesetscript.js and gets overriden in the custom frameset.  The only change here is the call to framesetsrcipt_showTimeoutWarningLogoff and that function simply calls application.logOff.


This issue is resolved through a local change. This can be tricky with PRPC 5.4SP2 and older User style portals. Please consider upgrading to the latest version of PRPC where portals are harness based and pxSessionTimer section can be used to properly accomidate such requirements. 


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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