Posted: 13 Apr 2016 20:37 EDT Last activity: 9 Jun 2016 6:21 EDT
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?
com.pega.pegarules.pub.PRMissingContextError: Cannot restore passivated page 'AuthReqContext' for Thread STANDARD
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?
I don't see a Page-Remove on AuthReqContext. We have seen similar issues in Pega 717, i.e. "passivated page could not be restored" and some of them fixed in Pega 718. You may want to open a SR with GCS to get these HFIXes in Pega 717 and this issue investigated, if they are needed.
Just to clarify, these are the fixes for core engine passivation logic, not specific to SAML. I checked the code in 7.2, there is no page-remove for that page either. So that may be necessary. Santosh Das, can you confirm?
My apologies for the delay. I have created SR-A24408 for this issue and have cross-referenced that SR to this mesh post as well. At this point, I can update the authentication activity to do the page-remove, I just need to know where that makes the most sense. Otherwise we would need this as a hot-fix. Thanks!
Oh - you think a new user is opening the same page as used by a person who has previously logged in. So doing the page-remove would then cause the system to not try to restore the page for the page-new? Am I understanding that correctly?
The activation is failing during the pySAMLWebSSOAuthenticationActivity activity and its throwing a PRMissingContextError exception. I do see that Pega is performing checkForPassivatedPage() under name 'AuthReqContext' ... sees that it exists and tries to read it with context of the current thread/Requestor.