No session-timeout in web.xml but still user is getting prompted for user name and password after 60 mins but business wants to keep it for 8 hours. Which setting is overriding access group settings in this scenario?
Thanks Shekhar for the reply. We are not using external authentication. I have gone through all these links and all of them are suggesting access group timeout setting is priority if we are not using external authentication but not sure which one is overriding.
What configuration in Authentication service we need to change? I could see a filed for timeout activity, but going through many timeout OOTB activities, I could not find any configuration related to timeout in those activities. Could you please tell how we can acheive this?
A user's access group is set to time out after 8 hours, but they see their session time out after 1 hour, displaying a modal window credential challenge. Putting in the user's Pega credentials does not log them back in.
STEPS TO REPRODUCE
Set a user's access group timeout to over 1 hour.
Wait one hour.
A defect or configuration issue in the operating environment. WebLogic has a default timeout of 1 hour if no timeout is explicitly set. After 1 hour, the WebLogic timeout is triggered, leading to the issue.
Make the following change to the operating environment: Set the WebLogic timeout in the web.xml in prweb.war (repackaging any .ear being used if neccesary):
Replace "480" with your desired WebLogic timeout, in minutes.