INC-130299 · Issue 583924
Updated SSO operator authentication handling after passivation
Resolved in Pega Version 8.1.9
With SSO enabled and the pyAccessGroupsAdditional value list populated with the Mapping tab, attempting to access an expired session with an old cookie resulted in a stale thread exception while mapping value list attributes. This was due to using an AuthServicePage which was created by another session thread that had become stale for current session, and has been resolved by updating the code to call the authenticateoperator method on the authservicepage copy.
INC-135874 · Issue 58341
Added handling for password containing a colon on Pega Client for Windows
Resolved in Pega Version 8.1.9
If a password included a colon (:), it was possible to log in on the desktop but not Pega Client for Windows. This was due to authentication files specific to the Windows mobility client, and handling has been added to resolve the issue.
INC-137709 · Issue 584291
New security role added to restrict access to development-specific classes
Resolved in Pega Version 8.1.9
A new security role and related RAROs have been implemented to allow better security for end users on non-BAC systems. This restricts access to Rules and execution of activities on classes that are development-specific.
INC-137978 · Issue 586184
CDK key loading modified for better database compatibility
Resolved in Pega Version 8.1.9
Users were unable to log on to the system and received the error "There has been an issue; please consult your system administrator." Investigation showed the log errors stating "(dataencryption.DataKeyProvider) ERROR localhost - Could not get CDK from systemKeyManagementCache - System CDK is null". This was an issue specific to the MS SQL Server database when there were 6 or more CDKs in the database: CDK keys are loaded from database into Cache using an SQL statement which had the ORDER clause. By default, the ORDER clause treats NULL values differently on different databases, and this caused MS SQL databases to not load a necessary CDK key. To resolve this, the SQL query has been modified so the result will be the same for all supported daatbases (Oracle, Postgres & MS SQL Server).
INC-138490 · Issue 591016
Handling added for samesite cookies with httpOnly
Resolved in Pega Version 8.1.9
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.
SR-D95148 · Issue 557485
Port validation updated for redirect URI
Resolved in Pega Version 8.1.9
When an offline app for windows client was generated, trying to login via SSO resulted in the error "invalid redirect_uri". This was traced to the system validating the whole loopback redirection URL, e.g. "http://127.0.0.1:1234/redirection", including the port number. To enhance flexibility, an update has been made so that the port number will not be validated, allowing the client to establish it based on availability at the moment of the request to the authorization service. NOTE: As a best practice, a loopback URL should not be configured as a redirect URI. If a loopback URL is configured, then at run time the port number will not be validated, and the client application can use any available port on the system including ports that may not be intended for use.
INC-133986 · Issue 585431
Encryption documentation updated for embedded properties
Resolved in Pega Version 8.6
Documentation updates have been made to provide instructions on configuring property encrypt policies for embedded properties. This includes information on creating two policies, on the class where the property is referred/used and on the final property level, so these properties can be smoothly encrypted/decrypted at all the places in the UI.
INC-137757 · Issue 600489
Primary page setting updated for micro DC container
Resolved in Pega Version 8.6
In Cosmos, a "Cannot Render Section" error displayed on submit of modal dialogue. This was caused by a primary page calculation error for the micro DC container, and has been corrected.
INC-138443 · Issue 584680
SAML authentication documentation expanded
Resolved in Pega Version 8.6
Documentation for SAML authentication services has been updated to include more detailed information about app alias URL changes.
INC-139085 · Issue 589553
Documentation updated for using Custom Stored Procedure after upgrade
Resolved in Pega Version 8.6
Documentation has been updated to reflect that when upgrading an environment to Pega 8.3+, the following two prconfig/DSS settings should be removed. This is the preferred approach to use the new ID generation mechanism. Additionally, if a database sequence was previously used to generate IDs, pc_data_uniqueid should be added or updated to make sure each case type has a row defined, and that the pyLastReservedID matches the maximum of the relative database sequence value plus 1. env name="pega/sequenceid/useOldOOTBIDGenerator" value="true" or DSS: prconfig/pega/sequenceid/useoldootbidgenerator/default env name="database/databases/customUniqueIDproc" value="sppc_data_uniqueid_custom" or DSS: prconfig/database/databases/customuniqueidproc/default To keep using the old custom stored procedure, the following settings should be given either through prconfig or DSS setting (prefixed with "prconfig/"). The sppc_data_uniqueid_custom can be replaced with a custom procedure name with the same signature as the standard stored procedure. env name="pega/sequenceid/useOldOOTBIDGenerator" value="true" env name="database/databases/customUniqueIDproc" value="sppc_data_uniqueid_custom"