Question
Has anyone experienced passivation errors with SAML Login?
I have not heard of user complaints, however we are seeing a number of these errors on a daily basis Cannot restore passivated page 'AuthReqContext' for Thread STANDARD( full java stack is below),
Note that this page is created by pySAMLWebSSOAuthenticationActivity and is used during the login process. Our timeout settings for users is set to 4 hours. I am wondering if, conceivably users are logging in, the AuthReqContext page is, after 15 min time or so, getting passivated, then if a user has been idle, the system tries to restore the page during the timeout re-authentication process? I do not see any PDN articles specific to this page being passivated. I wonder if the solution to this would be to simply put a page-remove in the pySAMLWebSSOAuthenticationActivity to remove that page once log-in is complete?
Caused by:
com.pega.pegarules.pub.PRMissingContextError: Cannot restore passivated page 'AuthReqContext' for Thread STANDARD
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.checkForPassivatedPage(ThreadPageDir.java:636)
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir$PageActivationPassivationListener.onBeforeAccess(ThreadPageDir.java:320)
at com.pega.pegarules.session.internal.mgmt.base.handler.AbstractPageHandler.onBeforeAccess(AbstractPageHandler.java:103)
at com.pega.pegarules.session.internal.mgmt.base.handler.UserPageHandler.getPage(UserPageHandler.java:153)
at com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory.getUserPageInCurrentDir(AbstractPageDirectory.java:189)
at com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory.getPage(AbstractPageDirectory.java:1061)
at com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory.getDirectPage(AbstractPageDirectory.java:672)
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.getDirectPage(ThreadPageDir.java:473)
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.getPage(ThreadPageDir.java:431)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.getPage(PRThreadImpl.java:513)
at com.pega.pegarules.session.internal.mgmt.Executable.findPage(Executable.java:2028)
at com.pega.pegarules.session.internal.mgmt.Executable.findPage(Executable.java:1981)
at com.pegarules.generated.activity.ra_action_pysamlwebssoauthenticationactivity_02ab975d06af72caead767130cb77400.perform(ra_action_pysamlwebssoauthenticationactivity_02ab975d06af72caead767130cb77400.java:157)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pega.pegarules.session.internal.mgmt.authentication.AuthenticationUtil.runActivity(AuthenticationUtil.java:208)
at com.pega.pegarules.session.internal.mgmt.authentication.SchemePRCustom.authenticateOperator(SchemePRCustom.java:695)
Message was edited by: Lochan to add Category
what is your prpc version? This could be due to some passivation error (search for PassivationDaemon in the logs) leading to the page not passivated successfully. Did you see any passivation related error?