INC-142648 · Issue 594806
PRTraceServlet security check added
Resolved in Pega Version 8.6
Modifying the Pega application URL with PRTraceServlet displayed multiple user credentials and session information. This has been corrected with the addition of a privilege check in GetConnectionListCommand before allowing the connections list to be fetched.
INC-143181 · Issue 599591
Handling added for terminate session exception caused by null operatorID
Resolved in Pega Version 8.6
After the REST service called ((PegaAPI)tools).triggerRequestorTerminationPulseEvent(action,OperatorsList,message), which was being used for maintenance by handling the REST request for terminating user sessions before the system was brought down, all login attempts were resulting in a null pointer exception and the system had to be restarted to recover. This was a corner issue caused when a NULL operator was provided as input, and has been resolved by adding handling for that case.
INC-144591 · Issue 601608
Oauth and beanutils jars upgraded
Resolved in Pega Version 8.6
The third party Oauth2 jars and commons-beanutils jar have been updated to the latest versions.
INC-144597 · Issue 598304
Updated handling for MT query of pr_data_admin table
Resolved in Pega Version 8.6
When using a multi-tenant environment with Oracle, as the number of users in the environment increased, the number of queries of the pr_data_admin table "WHERE pyEnableAuthService" increased exponentially and causes system slowness. This was traced to missed handling for the @ character in the authentication service cache while requesting, and has been resolved by updating authservicecache.java.
INC-144756 · Issue 602723
Security improved for searches
Resolved in Pega Version 8.6
Authentication requirements have been added to activities associated with searching.
INC-145033 · Issue 599479
ForgotPassword responses made consistent
Resolved in Pega Version 8.6
To prevent possible exposure of valid usernames, the ForgotPassword logic has been updated so that it will show the same messages and set of screens to both valid and invalid users if a lost password request is made.
INC-145694 · Issue 601293
Property check handling updated for Ajax requestor
Resolved in Pega Version 8.6
SECU0001 alerts were seen when submitting a case in the interaction portal. Logging indicated the errors were related to the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties which are included in an Ajax request when they exist in the DOM and the 'pyGeolocationTrackingIsEnabled' when rule is true. The error was traced to a condition where a new thread request results in an unexpected property check that encounters a clipboard which doesn't have any pages created for that thread. To resolve this, the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties have been added to an allow list to handle the unexpected properties check.
INC-146434 · Issue 602739
Accessibility added to Security Event Configuration headers
Resolved in Pega Version 8.6
Labels for the headers in the Security Event Configuration screen have been converted to dynamic layout headers so they will be detected by JAWS screen reader.
INC-146921 · Issue 601636
Cross site scripting update for Dev Studio
Resolved in Pega Version 8.6
Cross Site Scripting (XSS) protections have been added to Developer Studio.
INC-148117 · Issue 608005
Option added to return to same authenticationService after SAML logoff
Resolved in Pega Version 8.6
An enhancement has been added which provides a check box on the Authentication Service ruleform to select the option of redirecting users back to their original authentication service screen after logoff.