After upgrading MOVEit Automation to version 17.1.11, all login attempts to the Web Admin interface fail with "Invalid username and/or password", regardless of account type (administrator, service account) or login location (remote or localhost).

Despite the error message, the server logs confirm that credentials are valid. The session is established but then immediately terminated with a 400 BAD_REQUEST response. A SEVERE error in the logs indicates that the Apache Tomcat Native library version bundled with 17.1.11 (2.0.14) is incompatible with the Tomcat instance, which requires at least version 2.0.15.

Running a repair installation of 17.1.11 does not resolve the issue, as the incompatible library is part of the 17.1.11 installation package itself.

Version 17.1.11 of MOVEit Automation ships with an incompatible version of the Apache Tomcat Native library (2.0.14), while the bundled Tomcat instance requires at least version 2.0.15. This mismatch causes the Web Admin session to be terminated with a 400 BAD_REQUEST immediately after credential validation, producing a misleading "Invalid username and/or password" error on the login page even though authentication itself succeeds.

Upgrade MOVEit Automation to a version that contains the fix:

• 17.1.12 — recommended for customers on the 17.1.x branch
• 18.0.5 — recommended for customers on the 18.0.x branch

1. Log in to the Progress Software customer portal and download the installer for MOVEit Automation 17.1.12 or 18.0.5.
2. Run the installer on the affected MOVEit Automation server and complete the upgrade procedure.
3. After the upgrade completes, navigate to the Web Admin login page and confirm that login succeeds.

Misleading error message: The "Invalid username and/or password" message displayed on the Web Admin login page does not accurately reflect the failure. Server logs confirm that credentials are accepted; the session failure occurs at the session-establishment layer due to the Tomcat Native library incompatibility, not an authentication error.

Repair installation is ineffective: Running a repair of the 17.1.11 installer does not resolve the problem because the incompatible library is part of the 17.1.11 package itself.

Upgrading from a hotfixed 17.1.11 instance: Customers who received a hotfix build for an existing 17.1.11 installation do not need to re-apply any patch when upgrading additional servers. Installing 17.1.12 or 18.0.5 directly from the portal is sufficient, as the fix is incorporated into those release installers.