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-135849 · Issue 582939

Encrypted SOAP response token generation updated

Resolved in Pega Version 8.5.1

After configuring a SOAP service that used signature and encryption on the response, the response being created was incorrect and could not be decrypted by the receiver. Investigation showed that the API used to generate the SOAP headers was not setting the wsse11:TokenType element, causing receivers which enforce BSP compliance to fail. This has been resolved by modifying the custom webservices-rt-pega2 jar to set the token type in the case of a response encryption policy.

INC-138354 · Issue 584722

Handling added for samesite cookies with httpOnly

Resolved in Pega Version 8.5.1

After enabling samesite cookies on Google Chrome to support Mashup login, intermittent issues were seen with a non-mashup login where entering the OperatorID and password only resulted in a refresh of the login screen. This was traced to a scenario where an httponly cookie attribute was present along with samesite cookie attributes, and has been resolved by adding handling for a condition where samesite is set and httpOnly is enabled.

INC-130145 · Issue 582855

Null checks added for the presence of roles and dependent roles

Resolved in Pega Version 8.5.1

Frequent Null Pointer errors were being generated relating to SecurityAnalysisForSecurityAdministratorsTask.getCurrentSecurityTaskDetails(). Investigation showed that the Origin and Stack trace tabs were empty, leading to the obj-open of the role failing when the role was not available in the system being utilized. This has been resolved by adding a series of null checks for role existence and dependent roles existence.

INC-139867 · Issue 588757

Additional security for encrypted passwords

Resolved in Pega Version 8.5.1

Handling and cleanup has been updated for encrypted values to enhance security.

INC-134315 · Issue 578366

Resolved 400 error on second browser session

Resolved in Pega Version 8.5.1

When accessing application URLs in two tabs of a browser window, logging into the second session was throwing a 400 invalid request. This has been resolved by adding specified activities to an allow list which will bypass URLObfuscation in un-authenticated mode. Non-listed activities will be processed using URLObfuscation if it is enabled.

INC-130500 · Issue 580623

Cross-site scripting protections updated for authorization

Resolved in Pega Version 8.5.1

Cross-site scripting protections have been updated for various URLs associated with authorization.

SR-131072 · Issue 203709

Requestor token creation added for PRExternal authentication

Resolved in Pega Version 7.1.9

When using a PRExternal authentication scheme, the csrfsession requestor token was not created. This caused a heavy volume of INFO logging messages in production due to the null token. This authentication path has now been added and the token will be correctly created for use.

SR-131691 · Issue 202207

Improved performance for incorrect password handling

Resolved in Pega Version 7.1.9

When the operator entered the wrong password in the login screen, numerous "Stream Overwritten" alerts appeared the Alert log. There was no workflow problem involved, but the logging indicated that there was an additional unnecessary call being made to Stream Web-Login, and that unneeded call has been removed to improve system performance and remove the error being logged.

SR-A4056 · Issue 211550

Corrected validation error for Extract rule field length

Resolved in Pega Version 7.1.9

A validation error noting that the field length of the table was limited to 30 characters was occurring when trying to check in an Extract rule even if the field value had been shortened. While checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was recomputing the pagelist's table name instead of using the one provided by the user. The Rule-Utility-Function validateTreeProperties function has been modified to fix the issue.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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