Deprecating Anypoint connectivity assets affected by the Log4j vulnerability Planned deprecation of Anypoint Connectors that utilize the Log4J external library. There were vulnerabilities that were identified and fixed in the Log4J external library and all the affected MuleSoft connectors were updated as mentioned in the article: https://help.mulesoft.com/s/article/Deprecation-of-old-log4j-vulnerable-Anypoint-Connectors-April-2-2022
ATTENTION: up to 1 hour of service interruption is expected.
We will be performing a scheduled upgrade of an internal database.
* User Experience(UX): Runtime Fabric (Inbound Traffic tab): Unable to configure new or edit existing inbound traffic configuration. Tokenization: Unable to create or edit tokenization services Security: Unable to add or edit Tokenization Formats
*API Calls: Security fabric Edge APIs for inbound traffic configuration will not be accessible Tokenization APIs will not be accessible
*** ATTENTION: a 15 min to 1 hour service interruption is expected during this maintenance window … ***
We will be performing a scheduled upgrade on part of the platform's underlying infrastructure. *** Service impact details: * Applications: - Runtime Manager During the service interruption, there will be no impact to the applications. During maintenance downtime: * Runtimes: are not impacted. * User Experience(UX): Application management capabilities of Runtime Manager may be disrupted as some servers may be disconnected and become unavailable for management. This will be temporary and the correct state of the application will be reflected after the update has been completed. * API calls: API calls will not be impacted * Logs and Data: log and metric display data will be updated during the service interruption.
Posted Mar 24, 2022 - 10:45 PDT
This scheduled maintenance affected: Runtime Services (Runtime Fabric), Anypoint Management Center (Runtime Manager), and Anypoint Security (Tokenization).