SR-B46433 · Issue 305174
Email Listener waits for startup completion before beginning processing
Resolved in Pega Version 7.3.1
After restart all email listeners were shown as RUNNING in the SMA listener management view but did not download emails. Selecting RestartAll from this view then showed the old listeners still present and listed as STOPPING while new listeners were started. The new listeners processed the emails correctly. This has been fixed by updating the Email listener implementation such that during node start-up, email-listener will skip the e-mail message processing and sleep for a default polling interval (i.e. 90 seconds). After node startup completes, the email listener will start processing the email messages.
SR-B75335 · Issue 325035
Improved DSN message handling for Email Listener
Resolved in Pega Version 7.3.1
Email service was failing with a Gmail DSN message exception indicating Inbound data mapping had failed. To resolve this, logic has been added to Email Listener to ensure it properly processes the Gmail DSNs, In addition, error handling has been improved.
SR-B75335 · Issue 322757
Improved DSN message handling for Email Listener
Resolved in Pega Version 7.3.1
Email service was failing with a Gmail DSN message exception indicating Inbound data mapping had failed. To resolve this, logic has been added to Email Listener to ensure it properly processes the Gmail DSNs, In addition, error handling has been improved.
SR-B47240 · Issue 305940
File Listener enhanced to support source mask with two asterisks
Resolved in Pega Version 7.3.1
File Listener was not retrieving all files if the source name mask had more than one asterisk. Code has been added to support a maximum of two asterisks: one in the file name and one for extension, ex: *.RDM*.xml
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-B45960 · Issue 303751
Request & Response logs include POST method submits
Resolved in Pega Version 7.3.1
When using the POST method to send a request, request & response data was not showing up the in DEBUG logs of the Connect-REST execution. This has been corrected, and request & response data is now being added to DEBUG logs in Connect-REST execution.
SR-B49398 · Issue 306482
Request & Response logs include POST method submits
Resolved in Pega Version 7.3.1
When using the POST method to send a request, request & response data was not showing up the in DEBUG logs of the Connect-REST execution. This has been corrected, and request & response data is now being added to DEBUG logs in Connect-REST execution.
SR-B65744 · Issue 315671
Repaired use of custom case ID search
Resolved in Pega Version 7.3.1
After upgrade, custom search criteria for case IDs generated an error when pulling data from the database. This was traced to a change that removed CommonTLP as a fallback, and that default has been restored.
SR-B50950 · Issue 308958
Connect-SOAP passivation tuned
Resolved in Pega Version 7.3.1
Connect-SOAP implementation uses requestor instance to cache STSConfigContext and Axis2 ServiceClient objects; these are not serialize-able and were leading to requestor passivation failure. As part of the fix, these objects will be de-referenced from the requestor page and instead the system will use a requestor scoped data page to cache STSConfigContext and Axis2 ServiceClient objects.
SR-B55660 · Issue 316375
Removed "SHA1" hard coding from SAMLRedirectBindingHandler
Resolved in Pega Version 7.3.1
SAML logout failure was seen after using SHA256 signature encoding on an IDP that does not support SOAP. Previously,"SHA1" was hard coded to be used for verification of certificate during logout in the case of HTTP-Redirect Binding; this hard coding has now been removed from SAMLRedirectBindingHandler.verify() .