INC-204045 · Issue 694323
Signature map updated for fetching keys
Resolved in Pega Version 8.6.3
MFA login worked with SAML 2.0 when the certificate was disabled but failed when the certificate was enabled in Auth Service. The error " "Signature algorithm is null" appeared. This has been resolved by updating the signature map to ignore case sensitivity while fetching keys.
SR-D37894 · Issue 505975
Query parameters will be cleared after redirection from authentication
Resolved in Pega Version 8.2.5
When using the /PRAuth Servlet, running a snapstart URL generated from a secondary application correctly executed SAML Authentication and Pega processing, but a second URL generated with different parameters ran with the parameters from the first request. The third and subsequent requests processed as expected with the parameters sent in with the request. Investigation showed that the previous parameters were picked due to the query string parameters not being cleared after redirection, and this issue has been resolved by updating the system so it will clear the parameters after issuing a redirect from the authentication policy engine.
INC-200218 · Issue 692432
Added handling for calling truncate with external Cassandra
Resolved in Pega Version 8.6.3
A JMX exception was generated when using external Cassandra. This was traced to the combination of calling truncate and using external Cassandra for DDS, and has been resolved by adding a 'do not execute' consistency check during a truncate operation when using external Cassandra.
INC-187553 · Issue 675430
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.6.3
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
INC-188080 · Issue 673784
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.6.3
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
INC-188143 · Issue 674973
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.6.3
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
INC-189477 · Issue 674035
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.6.3
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
INC-200029 · Issue 690169
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.6.3
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
SR-D42406 · Issue 510669
Support added for UTF-8 charset in Connect-REST pyRequestAttachmentPage
Resolved in Pega Version 8.2.5
When using Connect-REST with pyRequestAttachmentPage, Polish characters like "ó" or "ł" were converted to "?". This did not happen when pyRequestAttachmentPage was not used. This was due to the post request body using a multipart handler that ignored the charset being passed in and considered it a respective enum type for Application/json internally instead. This has been resolved by adding support for charset UTF-8.
SR-D43918 · Issue 511182
Resolved duplicate task urgency
Resolved in Pega Version 8.2.5
Duplicate task urgency was displayed when using dynamic layout in non-template mode. Investigation showed that there were three 'when' rules used to display the task urgency based on an urgency value, and two of the 'when' rules were being returned as true, one of which was incorrect. This was due to an incorrect PropertyReferenceImpl object being passed when retrieving the value from the failSafe page because of an incomplete reference, and has been fixed.