SR-D2296 · Issue 436876
Enhancement added to support multiple security certificates
Resolved in Pega Version 8.3
When importing IDP metadata, the only the last verification certificate was imported if there were multiple certificates. This caused SAML SSO signing failures in some cases. Support has now been added for importing multiple certificates to enhance encryption security.
SR-D3556 · Issue 445684
Requestor.OperatorID page updated to stay in sync with current OperatorID to enable post-Auth activity mapping
Resolved in Pega Version 8.3
The systems pages were not getting updated to the right operator's context when a post-Auth activity was used for mapping. To support this use, the UpdateOperatorID trigger has been updated to keep the pxRequestor.OperatorID page in sync with the current operatorID page during SAML. The operator will also be saved during provisioning.
SR-B17037 · Issue 289405
Handling added for SP initiated logins
Resolved in Pega Version 7.3
Attempting a Service Provider (SP) initiated login request caused the error "The Response did not contain any Authentication Statement that matched the Subject Confirmation criteria" to appear. This was due to the code used to identify whether the flow is IDP initiated or SP initiated SSO not having the handling for encrypted assertions. The system has now been updated to look for the relay state in the DB: if an entry is present then the SSO flow will be SP initiated, otherwise it will be IDP initiated.
INC-157095 · Issue 638806
Enhancement added for tenant-level authentication
Resolved in Pega Version 8.6.1
In a multi-tenant PDC with a few tenants that utilize their own custom SSO, a pre-authentication activity inside a tenant that should block community access was also affecting tenants that did not have that pre-auth activity set. This was a missed use case and has been resolved by adding a tenantId hash in SchemePRAuth.makeUniqueSchemeName() to create the authServiceName.
INC-177737 · Issue 663140
Authentication requirement updated for CallConnector
Resolved in Pega Version 8.6.1
After update, invoking a REST API call during SSO login which eventually called pxCallConnector (Final Activity) in @baseclass Pega-RulesEngine failed at the CallConnector step. This was caused by a change in recent Pega versions which enabled authentication for this activity, and has been resolved by marking the activity as internal and disabling the authentication requirement.
SR-A99678 · Issue 272068
Chart clipboard page unloaded properly in tab refresh
Resolved in Pega Version 7.3
When a portal tab containing a chart was refreshed due to use of the "refresh when active" tabbed layout checkmark, the old chart clipboard pages remained. This was due to a missed use case, and has been fixed.
SR-B3591 · Issue 277488
Unit Test Case for DataPage localized for comma decimal indicators
Resolved in Pega Version 7.3
When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.
SR-B3591 · Issue 278006
Unit Test Case for DataPage localized for comma decimal indicators
Resolved in Pega Version 7.3
When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.
SR-B44878 · Issue 301248
displayHarness context maintained if established before passing pageName
Resolved in Pega Version 7.3
The runDataTransform() was running in the context of what was considered an incorrect page when called from the pre-js function of a Question shape when opening the case from the worklist. This was caused by using pega.offline.runDataTransform and passing the pageName parameter as null in an attempt to use the primary page context, but the system defaults to using the context of pyDisplayHarness instead of pyWorkPage when the pageName parameter is null. In order to support this configuration, the PreJS function of a question shape called from the displayHarness will maintain the context as displayHarness for pega.u.d.PrimaryPageName when passed.
SR-D45608 · Issue 519902
Correct service instance name passed for data flow in DSMStatus
Resolved in Pega Version 8.1.8
When using the Connect-HTTP service "DSMStatus" to provide the node and status information as seen on the various tabs of the Designer Studio > Decisioning > Infrastructure > Services landing page, using DataFlow as the service parameter for the HTTP service method resulted in an empty response when the expectation was to get the information regarding the cluster details of Dataflow node type. This was traced to the service instance name not being parsed correctly when used for Data Flow services, and has been resolved by ensuring the correct service instance name is passed for this use.