INC-178148 · Issue 660925
Handling added for SSO servlet name
Resolved in Pega Version 8.6.2
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
INC-188405 · Issue 673065
Handling added for SSO servlet name
Resolved in Pega Version 8.6.2
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
SR-B85132 · Issue 334749
SAML enhancements added with OperatorContext availability fix
Resolved in Pega Version 7.4
The activity pyEstablishOperatorContext availability was incorrectly marked as final. This has been fixed and is "Available, Extension". In addition, many other enhancements have been added towards the goal of no-code configuration of SAML SSO authentication. SAML SSO is the most widely used authentication in production, but has historically required complex custom code. Please see the release notes for more information about Single Page UI Configuration and Adaptive Design for Authentication Run-time.
INC-174267 · Issue 669672
Wait action persists when using Urgency Adjustment
Resolved in Pega Version 8.6.2
When using the Urgency Adjustment (pyAdjustAssignmentsla standard local action), once a case reached the wait action and the goal and deadline were updated the previous pyWaitAction was not being stored. This has been resolved by ensuring the previous pyWaitAction will be stored and passed to the AddAssign activity.
SR-B71077 · Issue 326659
IDP Encrypted connections working on SAML
Resolved in Pega Version 7.3.1
IDP initiated SAML 2.0 was not working, and generated the error "Unable to process the SAML WebSSO request : Missing Relaystate information in IDP Response". Authentication worked fine with unencrypted SAML token. This schema validation failure happened because encrypted attributes were previously being ignored by Pega due to an issue in the underlying openSAML library. To resolve this, a custom PegaSAMLValidator has been inserted to validate the assertion and honor encrypted attributes.
SR-B71077 · Issue 323027
IDP Encrypted connections working on SAML
Resolved in Pega Version 7.3.1
IDP initiated SAML 2.0 was not working, and generated the error "Unable to process the SAML WebSSO request : Missing Relaystate information in IDP Response". Authentication worked fine with unencrypted SAML token. This schema validation failure happened because encrypted attributes were previously being ignored by Pega due to an issue in the underlying openSAML library. To resolve this, a custom PegaSAMLValidator has been inserted to validate the assertion and honor encrypted attributes.
SR-B82203 · Issue 342014
Empty hidden elements stripped when AAR proxy in use
Resolved in Pega Version 7.4
When using IIS WebServer and AAR proxy configuration with high security settings, submitting a form through Microsoft Internet Explorer with hidden input fields that did not have a name attribute resulted in a blank parameter name and value being added. This formed an invalid request that returned a HTTP 200 with no error message. Because Microsoft Internet Explorer does not ignore elements which have empty names, the code has been updated to remove name attributes on pycustomerrorsection hidden elements.
SR-C757 · Issue 343486
Empty hidden elements stripped when AAR proxy in use
Resolved in Pega Version 7.4
When using IIS WebServer and AAR proxy configuration with high security settings, submitting a form through Microsoft Internet Explorer with hidden input fields that did not have a name attribute resulted in a blank parameter name and value being added. This formed an invalid request that returned a HTTP 200 with no error message. Because Microsoft Internet Explorer does not ignore elements which have empty names, the code has been updated to remove name attributes on pycustomerrorsection hidden elements.
SR-B79734 · Issue 344352
Summary report count fixed when using filter prompt
Resolved in Pega Version 7.4
The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.
SR-C2920 · Issue 344845
Summary report count fixed when using filter prompt
Resolved in Pega Version 7.4
The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.