SR-126719 · Issue 189646
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the trust store where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126719 · Issue 177348
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126719 · Issue 178793
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126775 · Issue 189860
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-127799 · Issue 192294
Included CMIS library updated
Resolved in Pega Version 7.1.8
Using Connect-CMIS Rule form, attempting to get a list of Repositories from a CMIS Server that allows Web service binding with Basic Authentication was failing with 401 - Unauthorized error. The getRepository operation succeeded when using SOAPUI or Apache Chemistry CMIS client Workbench. This was a defect with the particular CMIS library version included with Pega 7.1.7, and has been corrected by updating to a revised version.
SR-127838 · Issue 194007
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-127838 · Issue 194658
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-127237 · Issue 189891
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
SR-127549 · Issue 190837
Improved processing of WSDL for the Create SOAP Integration wizard
Resolved in Pega Version 7.1.8
When running the Create Soap Integration wizard for a selected operation from the WSDL, the wizard was not only generating the necessary rules for the selected operation, but for all operations in the WSDL. To address this, when processTypeContentsAndRelatives is processing a parent type, it now skips type substitutions of the parent.
SR-127743 · Issue 193331
Trace rule servicetype set for Service-File
Resolved in Pega Version 7.1.8
'Trace rule' for the Service-File is not working even though 'Trace rule' for Pega Service type worked correctly. This was caused by an inability to trace the Service-File due to not setting the servicetype, and the API has been updated to explicitly set the servicetype as "File" in ServiceAPI class.