Release notes for Optimizely CMS and Customized Commerce updates

Fixed an issue where warmup failed for a site page that had a mailto link.

Fixed an issue where Microsoft.Extensions.Diagnostics.HealthChecks version was deprecated and added a lot of logs inside application insights. Now, minor version of the Microsoft.Extensions.Diagnostics.HealthChecks is changed to 3.1. 

Fixed an issue where Warmup had a default value of MaxNumberParallelRequests set to 50, which in turn configured the HttpClient used by Warmup to set MaxConnectionsPerServer to 50. This value is too large and may cause thread starvation issues.

Now, this value is set to 10, and you can customize the idle timeout of connections used during warmup.

The minimum required version for Microsoft.ApplicationInsights.Profiler.AspNetCore dependency in EPiServer.CloudPlatform.Cms is increased to 2.6.0 so that the following bug no longer occurs: https://github.com/microsoft/ApplicationInsights-Profiler-AspNetCore/issues/202

Fixed an issue where the health check failed with InvalidOperationException.

Added an option to disable two cookies that get automatically added by Application Insights for a site visitor. All sites running on Optimizely DXP service have Application Insights enabled. Disabling the two cookies ensures that customers are GPDR compliant. Disabling the cookies makes some of the user tracking in Application Insights stop working, but Page View Tracking functions normally.

Fixed an issue where the health check service created separate parallel tasks (from HttpContext through IHttpContextAccessor) to perform a health check. 

Installing the EPiServer.CloudPlatform.Cms package on a .NET 7 project displayed a warning because it depended on a version of EPiServer.Azure that does not support .NET 7. This package should instead depend on EPiServer.Azure 11.1.

warning NU1608: Detected package version outside of dependency constraint: EPiServer.Azure 11.0.1 requires Microsoft.Extensions.Configuration.Abstractions (>= 6.0.0 && < 7.0.0) but version Microsoft.Extensions.Configuration.Abstractions 7.0.0 was resolved.

As a workaround, a direct reference to EPiServer.Azure 11.1.0 is added.

Updated EPiServer.CloudPlatform.Cms package reference to a non-deprecated version of Microsoft.ApplicationInsights.AspNetCore.

On DXP, clients can use KeyVault for data encryption and decryption. There are two ways for KeyVault authentication:

• Environment credentials – TenantID, ClientId, ClientSecret.
• Managed identity – Clients can create an identity object with a username and assign it to relevant roles, then use the object for KeyVault authentication. Using managed identity is a popular approach now for authentication as it is a simpler way to set up information than environment credentials. See Manage identity types on the Microsoft website.

Currently, to add data protection for BLOB, clients call the AddDataProtectionToBlobStorage() extension method, which instantiates DefaultAzureCredentialOptions.  The instance contains information about environment credentials and managed identity for KeyVault authentication. By default, environmental credentials are prioritized first, and then, if the authentication fails, the managed identity started to be used. This causes an inconvenience for clients because they prefer using managed identity (more modern and popular than environment credentials).

By default, you should ignore environmental credentials in authentication and instead, use managed identity by creating the instance by using the following code line in the extension method:

{{new DefaultAzureCredentialOptions

}}