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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-209298 · Issue 704141

Added security tokens to Worklist assignment error wizard

Resolved in Pega Version 8.6.4

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.

INC-211426 · Issue 706061

UI and code changes to support Client Assertion in Open ID Connect

Resolved in Pega Version 8.6.4

In order to support private_key_jwt, an enhancement has been added which will pass the “Client ID” and “Client assertion” (in the form of a signed JWT) as part of the authorization code grant flow for an IDP-initiated SSO. The Authorization Server will then authenticate Pega (the client) to verify the signature and payload of assertion by retrieving the public key via Pega’s JWKS endpoint.

INC-215343 · Issue 711141

Security updates

Resolved in Pega Version 8.6.4

Security updates have been made relating to rulesets using allow lists, checks for Java code injections, SAML-based SSO code, and supporting SFTP as part of the validation in the pxValidateURL rule.

SR-A102969 · Issue 273954

XSS security update for error.jsp

Resolved in Pega Version 7.3

The error.jsp file has been updated for better XSS security with WebSphere and Firefox.

SR-A96514 · Issue 275326

Updated encryption logic for URL obfuscation

Resolved in Pega Version 7.3

If URL obfuscation was enabled and the incoming URL had non-ASCII characters (or UNICODE) characters in it, the encryption process was failing due to the incorrect length of byte array formation in padding logic. This logic error has been corrected.

SR-A97323 · Issue 266550

XSS filtering added to pzDisplayModalDialog

Resolved in Pega Version 7.3

XSS filtering has been added to the pzDisplayModalDialog to improve security.

SR-B10697 · Issue 282917

XSS handling added for pyCategory in Rule-Obj-Listview.ListViewHeader

Resolved in Pega Version 7.3

Cross-site scripting handling has been added for the pyCategory parameter in ListViewHeader to improve security.

SR-B10697 · Issue 280753

XSS handling added for pyCategory in Rule-Obj-Listview.ListViewHeader

Resolved in Pega Version 7.3

Cross-site scripting handling has been added for the pyCategory parameter in ListViewHeader to improve security.

SR-B10947 · Issue 280020

pzSUS Param properly URLEncoded

Resolved in Pega Version 7.3

The Tomcat 8+ server was rejecting DWA URLs due to characters such as {,} that it considered to be unsafe. These characters were introduced by pzSus key in the URL, and these values will now be encoded for the browser to resolve these issues.

SR-B11243 · Issue 284444

XSS handling added for ShowSelectedPortal in RedirectRun

Resolved in Pega Version 7.3

XCC handling has been added to the RedirectRun activity using location parameter and ShowSelectedPortal to improve security.

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