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.

INC-148056 · Issue 602837

Context updated for IACAuthentication activity trace

Resolved in Pega Version 8.3.5

After upgrade, tracing the IACAuthentication activity was not working. Investigation showed that the context object had a null tracer value, which has been resolved by updating the system so the tracer runs with the correct context.

INC-140224 · Issue 604005

Corrected SAML SSO error

Resolved in Pega Version 8.3.5

After opening a case from the Pega-FCM portal or after logging in from SSO, closing the Pega window and opening it again resulted in the error "Unable to process the SAML WebSSO request : Violation of PRIMARY KEY constraint %27pr_data_saml_requestor_PK%27. Cannot insert duplicate key in object". This was a missed use case that happens only under the old SAML configuration, and has been resolved by removing a when condition that checks for stepstatus fail for the pySAMLwebSSOAuthentication activity.

INC-135437 · Issue 589489

Export to Excel working for reports with "Display values across columns"

Resolved in Pega Version 8.3.5

Attempting to use Export to Excel when "display values across columns" was checked resulted in a null pointer error. This was traced to a null page being passed to pzRDExportWrapper, and has been resolved by adding a check for the primary page If it is null, the step page will be used.

INC-145033 · Issue 599481

ForgotPassword responses made consistent

Resolved in Pega Version 8.3.5

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-137873 · Issue 596158

Java injection security updated

Resolved in Pega Version 8.3.5

Protections have been updated against a Java injection.

INC-142531 · Issue 598438

Keystore certificate alias updated to support mixed case names

Resolved in Pega Version 8.3.5

The Java Keystore stored aliases only in lower case letters, but it accepted uppercase letters also during retrieval. This was causing the error "No certificate found in truststore : Azure AD SSOIDPCertStore with Alias : CN=Microsoft Azure Federated SSO Certificate" when the names didn't match. To resolve this, the keystore layer has been modified to support upper case letters in the certificate alias.

INC-133450 · Issue 585994

Login button hidden after click

Resolved in Pega Version 8.3.5

When the login button was clicked fast several times, intermittently the login would fail with the blue screen and "Security violation attempting to access requestor" error in the logs. To resolve this, on click of the login button will be hidden to prevent firing multiple login requests.

INC-144591 · Issue 601614

Oauth and beanutils jars upgraded

Resolved in Pega Version 8.3.5

The third party Oauth2 jars and commons-beanutils jar have been updated to the latest versions.

INC-134808 · Issue 590713

Property check handling updated for Ajax requestor

Resolved in Pega Version 8.3.5

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-140101 · Issue 597636

System will attempt to decrypt data ending in "+"

Resolved in Pega Version 8.3.5

Encrypting and decrypting one specific email address was not working properly when showing on the UI. It was possible to force a decryption using decryptproperty, but Pega generated an error. This was due to the actual encrypted value ending with '+', which conflicted with a system check that skips decryption if the encrypted property value ends with + . To resolve this, the system will attempt to decrypt the property even when encryptedText ends with + .

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us