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-121444 · Issue 561810
Added handling to force text area maxlength in Microsoft Edge
Resolved in Pega Version 8.1.9
When using the Microsoft Edge browser, it was possible to continue entering characters in excess of the value set for the 'max characters' property. Investigation showed that the Microsoft Edge browser does not honor the maxlength attribute on text area; to resolve this, logic has been added to restrict the user from entering extra characters above the max limit.
INC-125334 · Issue 581939
Focus persists for embedded Tab Group layout with section refresh
Resolved in Pega Version 8.1.9
When a Tab Group Layout was configured with multiple sections using multiple input elements including one with a 'Refresh this section' action, using the Tab key to reach the input element, make a change, and hit Tab again caused the focus to reset to the top input element. This has been corrected.
INC-125398 · Issue 564978
Updated handling for checkboxes configured in the header
Resolved in Pega Version 8.1.9
After configuring multiple checkboxes where each checkbox had a different property and different DT as action set and then using them as a single column header in the table, the on-change of any one checkbox caused all of the checkboxes to be checked or unchecked in the column header. This was caused by the pega.ui.grid.prototype.checkAllIfInHeader, which selects or unselects all checkboxes present in table (header +. body) based on checkbox status in header. However, the header row should not be part of the iterator during this function, and the necessary update has been made.
INC-126255 · Issue 580910
Resolved "maximum limit for pending changes" error
Resolved in Pega Version 8.1.9
When attempting to create a work object in a custom way using doCreateNewCase from the Smart investigate layer by using the RMButtonWithoughtWorkCaseNGP section, a popup showed the error “You have reached maximum limit for pending changes. Please commit/cancel one or more changes to continue.” The error did not occur when creating the case using the out-of-the-box Create New Work action. This was traced to the custom configuration creating work object threads that were not destroyed after the work item is closed. To resolve this, handling has been updated for passing dynamiccontainerID and contentID parameters for OpenWorkByURL case. Note that the pzUpdateActionInfo activity must be called in any custom activity before the actual activity is invoked.