Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-225840 · Issue 730754

Key ID made optional for JWT

Resolved in Pega Version 8.8

After update, Connect-REST services were failing with a Admin_Security_Token.Action error. This was traced to kID (key ID) being mandated following previous work done to address an issue. To resolve this and better support backwards compatibility, the kID has been made optional in the JWT header.

INC-226479 · Issue 727465

Cross-site scripting filters added to redirect parameters

Resolved in Pega Version 8.8

Cross-site scripting protections have been added to Param.redirect to improve security.

INC-227736 · Issue 744475

Added polling lock to handle CDK Key rotation issues

Resolved in Pega Version 8.8

An error was generated when attempting to open existing encrypted contacts created in the Sales Automation application. This was traced to multiple nodes generating CDKs simultaneously, leading to a race condition, and has been resolved by refactoring the CDK generation code so it will acquire a lock when polling the database to avoid a race condition.

INC-227769 · Issue 731726

ReloadHarness security updated

Resolved in Pega Version 8.8

Security handling has been updated for ReloadHarness to ensure proper CSRF validation.

INC-228169 · Issue 729003

Login error messages updated

Resolved in Pega Version 8.8

Exception response messages have been updated in order to improve security around attempts to bypass operator authentication.

INC-232970 · Issue 742011

Security update for MashUp

Resolved in Pega Version 8.8

Cross site scripting protections have been updated for the LoadMashupPage activity and RedirectTo parameter.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us