Posted: 16 Aug 2018 14:25 EDT Last activity: 23 Aug 2018 9:52 EDT
Pega-RULES Web Cookie Causing Issues
I am having issues thisat I have been able to narrow down I think to the Pega-RULES cookie. This was originally seen as an issue with a Pega mashup that is using SSO. The problem was when it was calling for the script that is needed for the mashup the browser would put up a prompt asking for authentication. Navigating to the Script resource, Designer studio login or any other public pega resource is getting a prompt to sign in to pega. By clearing the Pega-RULES cookie and refreshing the page either on the mashup or on the development sign in, the page will reload just fine with a new value for the Pega-RULES cookie. I have proved this on multiple browsers as well. What seems to be happening is that if the browser is open for some time it times out after what feels like 20 or 30 minutes. If after that, the Pega-RULES cookie needs removed and then the resource is able to be gotten to. This cookie is removed at the end of the browser session.
All this said, why is the Pega-RULES cookie apparently blocking our environment and why is removing it helping the pages to load. Of course when the page refreshes the cookie comes back with a new value and everything works fine again - until it breaks and the process has to be repeated. This will not fly in a production environment where a user would have to know to clear their cookies for it to be accessed again.
***Edited by Moderator Marissa to update platform capability tags****
Looks like you are running into timeout issues when redisplaying the Mashup.
Are you using the /IAC servlet and IACAuthentication AuthService? The timeout by default OTB for the IACAuthentication AuthService as defined on the Custom tab is set to "Use Basic Authentication for Timeout".
If the users AccessGroup has a timeout value defined on the Advanced tab and the user has been idle, no communication to Pega has been made in the timeframe, the user will be prompted for user credentials on next request.
If you remove the timeout value in the AccessGroup you shouldn't run into this issue.