Chapter 5. MTA 6.2.0

Integration with JIRA

The integration of Migration Toolkit for Applications with Jira allows you to track and manage the whole migration process. To introduce changes to the applications in the portfolio, you can create issues in Jira and assign them to developers.

Migration Waves management

A migration wave is a small collection of workloads that deliver business value. MTA’s Migration Wave groups applications to be migrated on a specified schedule.

OpenShift Monitoring integration

MTA integrates with OpenShift Monitoring, which allows users to consume metrics from their MTA installation.

CVE-2023-44487: Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack)

A flaw has been found in handling multiplexed streams in the HTTP/2 protocol. The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can be reset multiple streams quickly. The server has to set up and tear down the streams while not hitting any server-side limit for the maximum number of active streams per connection, which resulted in a denial of service due to server resource consumption.

CVE-2023-39325: Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack in the Go language packages)

The HTTP/2 protocol is susceptible to a denial of service attack because request cancellation can reset multiple streams quickly. The server has to set up and tear down the streams while not hitting any server-side limit for the maximum number of active streams per connection. This results in a denial of service due to server resource consumption.

Re-enabling Keycloak breaks MTA

Keycloak is enabled by default. If you disable and then re-enable Keycloak, you cannot perform any actions in the MTA web console after logging in again.

Analysis fails when fetching rules from a repository with a folder that contains spaces in its name

When fetching custom rules from a repository during an analysis, if the Root path field contains spaces, the mta-cli command is not properly composed and the analysis fails. MTA-458

Update notifications are disabled for Application, Job functions, and Business services

Update notifications are disabled for Application, Job function and Business services, as a result, no notifications are displayed. MTA-1024

Repository type field is not required

The Repository type field is not required when saving the configuring rules files from a repository in analysis. MTA-1047

False 'not connected' status for new Jira instance

When creating a new Jira instance, the connection status is initially shown as Not connected before it moves to Connected, and this delay could cause the user to think that the provided credentials are incorrect. MTA-1019

Analysis wizard

The release of MTA 6.2.0 resolves the issue that Analysis wizard was stuck on the custom rules page on moving Back from the Repository tab. For more information on this issue, see MTA-464.

Tags & Reports tabs

The release of MTA 6.2.0 resolves the issue that an analysis was running for an application, and after clicking on that application to see the Tags and Reports, both the tabs keep loading until the analysis finished. For more information on this issue, see MTA-465.