INC-184964 · Issue 705935
TextMask_Encrypted rule added for use with Oracle
Resolved in Pega Version 8.5.6
When a property was being encrypted by propertyEncrypt access control policy and masked by propertyRead access control policy, it showed a "@@getMaskedValueOfText" error. This has been resolved with the addition of a new rule pxTextMask_Encrypted for Oracle product type which will remove extra spaces from the SOURCE string to handle ORACLE specific usecases.
INC-185251 · Issue 674905
Locking APIs updated to handle CDK key rotation
Resolved in Pega Version 8.5.6
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 668824
Keystore update properly revises the cache
Resolved in Pega Version 8.5.6
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-186395 · Issue 701424
Updating handling for for Pega-supplied operators with MFA
Resolved in Pega Version 8.5.6
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-186897 · Issue 681029
DSS DisableAutoComplete setting honored
Resolved in Pega Version 8.5.6
Setting DisableAutoComplete DSS was not working as expected. This was traced to the system not being able to read the DSS value due to timing related to database startup, and has been resolved by directing the system to read the setting in PREnvironment.java instead of from the prconfig.
INC-188128 · Issue 671827
Refresh assignment checks updated
Resolved in Pega Version 8.5.6
Additional privilege checks have been added to refresh assignment.
INC-188676 · Issue 696580
Improvements for Report Definition OperatorID filtering
Resolved in Pega Version 8.5.6
Report Definition filters were not working as expected when data from the OperatorID page was used and authentication was enabled. This was traced to the OperatorID page not being correctly populated. To resolve this, the authentication logic has been modified to always create the OperatorID page at requestor level, and the HTTP API layer has been updated to remove the thread level OperatorID page if exists. In addition, an enhancement has been added for improved debugging on log appenders provided by log4j which allows log filtering based on the requestor and thread for a given appender at a specific log level.
INC-188889 · Issue 675579
New application wizard security updated
Resolved in Pega Version 8.5.6
Security around displaying and running the new application wizard has been enhanced.
INC-190368 · Issue 673966
JWT access token key rotation handling updated
Resolved in Pega Version 8.5.6
When using the JWT token, REST services were randomly failing with the error message "Error in Processing JWT". Investigation showed the JWT access token key rotation data which was generated was not propagated to all the nodes. This has been resolved by updating the ORDER BY applied on KEYPAIR_CREATE_TIME_PROP. In addition, the default key pair rotation time has been increased from 15 to 90.
INC-190384 · Issue 676572
URL validation updated to handle custom token endpoints
Resolved in Pega Version 8.5.6
While saving an authentication profile with OAuth details, validation was failing for a valid URL given in the access token endpoint and revoke token endpoint fields. This was traced to the use of the Apache URL validator, which considered some domains to be invalid. To resolve this, the urlvalidator constructor has been updated to include a custom RegexValidator for access token and refresh token URLs.