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-202122 · Issue 691804

Logging extended for unexpected properties received in HTTP request

Resolved in Pega Version 8.5.6

Additional logging has been added to assist with tracing SECU0001 alerts seen when submitting a case in the interaction portal.

INC-204886 · Issue 698157

Log4j file security vulnerability issue addressed

Resolved in Pega Version 8.5.6

A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability .

INC-204897 · Issue 696149

Log4j file security vulnerability issue addressed

Resolved in Pega Version 8.5.6

A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability .

INC-206288 · Issue 705270

Addressed intermittent Issues with OAuth2

Resolved in Pega Version 8.5.6

Issues with logging in to a node by way of the access token endpoint were related to the error "JSON web token is rejected during signature verification due to bad signature". This has been resolved by adding clock skew value to the JWT processor bean during validation.

INC-209298 · Issue 704143

Added security tokens to Worklist assignment error wizard

Resolved in Pega Version 8.5.6

After enabling CSRF, moving to 'Configure -> Case Management -> Tools -> Work Admin -> Worklist assignment errors' and then selecting a record and clicking on 'Delete' resulted in a '403 Forbidden' error. This has been resolved by adding CSRF and fingerprint tokens as part of the form data.

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