Optimizely - update 444

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

}}

Fixed an issue where the profiler in Application Insights failed with the following stack trace:

fail: Microsoft.ApplicationInsights.Profiler.Core.UploaderProxy.UploaderPathProvider[0]
       Uploader can't be located.

This was a Optimizely Content Management System (CMS 12) app that was using EPiServer.CloudPlatform.Cms v1.3.

Fixed an issue that did not update a token in the cache when the session ID expired and used an expired token to retry authentication.

Fixed an issue that did not update a token in the cache when the session ID expired and used an expired token to retry authentication.

Fixed an issue where Norwegian translations for TinyMCE was not loaded or contained incorrect translations. TinyMCE 3 has an issue where Paragraph had an incorrect translation and this was fixed with TinyMCE 4 but the resources were not correctly loaded. For correct Norwegian translations upgrade to latest TinyMCE 4 version.

Fixed an issue that inserted a default alt text value of Content Name when you dragged or uploaded an image into TinyMCE.

Fixed an issue where TinyMce 4.0.0 could not localize using XML files in languagefiles folder.

Fixed an issue that inserted a default alt text value of Content Name when you dragged or uploaded an image into TinyMCE.