SR-A92057 · Issue 259453
OneTimeUse cache file generation disabled for SAML2
Resolved in Pega Version 7.2.2
Whenever SAML2 Token contained a "OneTimeUse" caching condition there were thousands of unwanted files generated. This caching has been disabled in the assertion validation code of SAMLv2ResponseProtocolValidator.java, so even if SAML2 token contains that OneTimeUse condition these files will not be generated.
SR-A76677 · Issue 253493
IDP SAML 2.0 schema validation error resolved
Resolved in Pega Version 7.2.2
When generating the Pega SP metadata after importing the Shibboleth IDP metadata, the error "The metadata does not pass the SAML 2.0 schema validation" appeared. This has been resolved by modifying the pzDownloadSPMetadata activity to generate a unique secure random ID prefixed with an underscore.
SR-A89074 · Issue 258503
Resolved upgrade issues with ConnectSOAP using MTOM
Resolved in Pega Version 7.2.2
After upgrading, Connect SOAP request messages were failing on the back end server with the error "xop 3.2.2.a: xop:Include must be the sole child of element" . Analysis showed the base64binary was not being substituted correctly with the expected "XOP Include" element. Axis uses Axiom to write Multipart messages and multiple XOP writers are involved in writing and encoding the message. When the writer stream is flushed , it depends on SimpleNsStreamWriter to write the bytes. SimpleNsStreamWriter is currently packaged as part of WStx-2.3-asl.jar and webservices-rt.jar, but this was not true in previous versions. As a result after upgrade, Webservices-rt classes is taking precedence over wstx-asl classes, which was generating the XOP:include elements with inline content. For better backwards compatibility, the WS-TX jar references have been removed from the webservices-rt.jar so that now it will rely on wstx-asl-3.2.3.jar which is already shipped with the product.
SR-A93295 · Issue 260100
Page-Copy given 'when' rule for assembler switch
Resolved in Pega Version 7.2.2
Performance issues relating to XML stream assembly were identified as an assembler switch problem in the Page-Copy Activity Method step. To improve response, a 'when' rule has been instituted to control switching between the old assembly Action aspect or the Model aspect in a scoped way, but can be overridden in the parse XML rule applies-to class.
SR-D41229 · Issue 513589
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.2.6
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D54314 · Issue 517290
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.2.6
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D58964 · Issue 520129
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.2.6
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D63579 · Issue 527999
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.2.6
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D65362 · Issue 526932
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.2.6
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D72368 · Issue 534330
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.2.6
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.