INC-181812 · Issue 667197
SSLContext created using protocol from REST connector rule form
Resolved in Pega Version 8.7
After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead.
INC-183485 · Issue 685269
Performance improvement for offline mobile app
Resolved in Pega Version 8.7
Performance issues on an offline mobile app were traced to an empty browser fingerprint caused by a declared variable which was not assigned a value. This has been resolved by adding a !pega.offline check for fireDeferredAsyncRequests.
INC-184804 · Issue 667544
Password security enhanced
Resolved in Pega Version 8.7
Security and authentication have been enhanced for password handling.
INC-185251 · Issue 674906
Locking APIs updated to handle CDK key rotation
Resolved in Pega Version 8.7
it was not possible to save cases for several hours following the CDK key rotation. This was traced to an exception that caused the system to attempt to acquire a lock on the CDK key instance, and normal save behavior would resume after the default sys lock time out period expired. This has been resolved by updating the system to use LockManager APIs to perform a database save with locks.
INC-185362 · Issue 668826
Keystore update properly revises the cache
Resolved in Pega Version 8.7
A keystore updated with the latest certificate was not getting reflected in the runtime and the old certificate was getting picked. In a multi-node environment when the new JKS is uploaded in one node, the changes are expected to be communicated to other nodes so that the cache can be cleaned up. In this case, investigation showed that the keystore label was in uppercase and the cache entry was not correctly removed. This has been resolved by adding an update that will convert the cache key to lowercase and maintain uniformity to ensure proper cleanup.
INC-185482 · Issue 670107
Certificate expiration notice toggle correctly updates
Resolved in Pega Version 8.7
Clicking the Configure notifications for expiring certificates toggle to switch it off was still showing the toggle as on after refresh. This has been corrected
INC-185514 · Issue 668029
Certificate expiration notice toggle correctly updates
Resolved in Pega Version 8.7
Clicking the Configure notifications for expiring certificates toggle to switch it off was still showing the toggle as on after refresh. This has been corrected
INC-186395 · Issue 677205
Updating handling for for Pega-supplied operators with MFA
Resolved in Pega Version 8.7
When a site is blocking prweb and using prweb/PRAuth for login with MFA enabled, admin user id logins failed and MFA showed the error screen for Pega-supplied users. This was due to MFA verification not being configured for Pega-supplied operators, and has been resolved by adding an Adminstrator condition to skip MFA for for Pega-supplied operators.
INC-186512 · Issue 669328
Password security enhanced
Resolved in Pega Version 8.7
Security and authentication have been enhanced for password handling.
INC-188128 · Issue 671829
Refresh assignment checks updated
Resolved in Pega Version 8.7
Additional privilege checks have been added to refresh assignment.