We are using Pega 8.2.1V and Saml 2.0 authentication service. OKTA is the authentication provider.
We are getting blue screen like Pega login screen if we lost the pega session (Requester page is classless) or OKTA session time out. So we need to do exception handle like to suggest user to close the browser session and login with new session for the blue screen scenario. So we are unable to trace here because session is not available. Can you please suggest any Pega OOTB/build rules to achieve this requirement.
Few users are facing the issue in prod as for the below scenario.
if the user is ideal/inactive state in more than 2 hours then we are getting blue screen popup like user unauthenticated if we access any functionality on the end user screen.
If the user is try to switch the access group under the user portal with different JVMs then we are getting blue screen like user unauthenticated.
These issues are coming only for few users not for all.
***Edited by Moderator Marissa to change type from General to Product, update Product details and Platform Capability tags****