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.

SR-D62949 · Issue 527502

XSS protection added

Resolved in Pega Version 8.4

The CrossScriptingFilter API has been applied to address a potential XSS issue related to stream rule parameters used in the request header.

SR-D63232 · Issue 524295

Support added for Authentication service rule attributes in embedded pages

Resolved in Pega Version 8.4

SSO login was not working, giving the error "Unable to process the SAML WebSSO request : No value specified for Attribute in SAML assertion". Investigation showed the Authentication service rule could only map attributes that are on the top level page and did not consider embedded page values. To resolve this, tools.getProperty will be used to fetch the property reference value instead of find Page and getString.

SR-D63727 · Issue 531726

Authorization header base 64 format error recategorized as debug logging

Resolved in Pega Version 8.4

Numerous messages were generated indicating that the Authorization Header format was invalid when using the format " : " (Base64 Og==) . As this is the default behavior for a particular class of proxy servers, the error statement has been updated to be logged as a debug statement and will be visible only when that logging is enabled.

SR-D71378 · Issue 533282

Authorization header base 64 format error recategorized as debug logging

Resolved in Pega Version 8.4

Numerous messages were generated indicating that the Authorization Header format was invalid when using the format " : " (Base64 Og==) . As this is the default behavior for a particular class of proxy servers, the error statement has been updated to be logged as a debug statement and will be visible only when that logging is enabled.

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