SR-C70146 · Issue 407968
Corrected SAML SSO logout error
Resolved in Pega Version 8.1.2
When performing a SAML SSO Logout, an error appeared indicating some artifacts were missing. This was traced to an incorrect NameQualifier being generated with IDP in the logoff request, and has been fixed by modifying the code to include an SPNameQualifier attribute for the NameID element in the logout request. Namespace has been added for logout requests at the parent level instead adding it at each node element.
SR-C65438 · Issue 406711
Added SAML parameter page generation for local use to bypass null auth object
Resolved in Pega Version 8.1.2
After defining any step which used parameters in the Post authentication activity of a SAML authentication service, the authentication failed with a java.lang.NullPointerException at com.pega.pegarules.session.internal.mgmt.Executable.putParamValue(Executable.java:3030). This was traced to local logic inserted to iterate through the SAML attributes that used a null parameter page. To resolve this, code has been inserted that will generate a new parameter page for the iteration rather than getting it from the authentication object.
SR-C64783 · Issue 407089
Corrected handling for SAML logoff
Resolved in Pega Version 8.1.2
On SAML logoff, the error "There has been an issue; please consult your system administrator; Status:fail ... No certificate found in truststore" appeared. Investigation showed this was an issue with the aliasing of certificates and signing that led to the requestor not being terminated for that logoff response. To correct this, when Pega receives a logout request which is invalid, it will terminate the session instead of throwing a PRRunTimeException.
SR-128883 · Issue 195834
Fixed button contrast when using accessibility
Resolved in Pega Version 7.1.8
The "Select Values" button in the dialog to edit report filter had a low contrast ratio when accessibility was enabled. This was caused by the unintentional application of the repeat layout CSS to the button, and has been fixed.
SR-130224 · Issue 200002
Fixed class pickup when Ticket Urgency is used as reference
Resolved in Pega Version 7.1.8
It was not possible to convert a summary report to a list report if the report had Ticket.Urgency as a reference and Ticket was a single page pointing to data class type property in the work class. This was traced to the drill down picking up the Urgency property from the work class, and has been resolved.
SR-C65757 · Issue 404535
Support added for POST binding in SAML logout
Resolved in Pega Version 8.1.2
Enhancements have been added in code and rule changes to support POST binding for SAML logout. In addition, handling has been added to resolve an ArrayOutOfIndexException error that was appearing if IDP sent parameters without any value.
SR-C65757 · Issue 406953
Support added for POST binding in SAML logout
Resolved in Pega Version 8.1.2
Enhancements have been added in code and rule changes to support POST binding for SAML logout. In addition, handling has been added to resolve an ArrayOutOfIndexException error that was appearing if IDP sent parameters without any value.
SR-119772 · Issue 175593
Menu rendering corrected for Attachment Menu controls when using JAWS
Resolved in Pega Version 7.1.8
Previously, the 'add menu' button in the Attachment Menu controls did not respond to the spacebar or enter key if JAWS was active. This was due to a rendering issue with the work flow menu options and has been resolved.
SR-C62434 · Issue 410619
Optimize Schema Index Creation updated to use Admin Datasource when available
Resolved in Pega Version 8.1.2
When configured according to the Pega Installation Guide, the SQL Server base user did not have the ALTER privilege enabled on the data schema. The Optimize Schema Index Creation was using the base user datasource "jdbc/PegaRULES" instead of the admin datasource "jdbc/AdminPegaRULES" even though an admin connection was available. This was an oversight during development, and has been fixed by modifying NoDBAUtils.java to use an admin connection if one is available. In addition, a clarification has been added to the UI to alert the user that an optimization job has been scheduled rather than completed.
SR-C70757 · Issue 411814
Added null check to resolve error when using datapage as dropdown source
Resolved in Pega Version 8.1.2
The user application was hanging with the browser console error "Uncaught SyntaxError: Unexpected end of JSON input" when using Dropdown controls with Datapage as a source in conjunction with parameterized datapages to create a cascading second dropdown. This did not happen when using any other data sources for the same control dropdown. This has been resolved by adding a null check at the reloadcell response.