Configure Web Admin FIPS mode
- Last Updated: April 13, 2026
- 3 minute read
- MOVEit Automation
- Version 2026
- Documentation
Enabling FIPS mode for Web Admin connections ensures that only FIPS validated cryptographic algorithms are available. To enable or disable FIPS mode for Web Admin on new installations and upgrades from 2024.1 or later, complete the procedures detailed below.
Note: MOVEit Automation 2024.1 was updated to using a 3.x
OpenSSL FIPS provider. This update impacts how OpenSSL gets ciphers and encryption
algorithms used to connect to Web Admin. If you have enabled FIPS mode for Web Admin
in an earlier version, after upgrade you must complete the steps below to continue
to work with FIPS mode enabled.
If upgrading a system where Web Admin FIPS-mode is already enabled to MOVEit Automation
2024.1 or later, to ensure that Web Admin FIPS-mode continues to function, make note of
the following points:
- You must complete the enable Web Admin FIPS-mode procedure to satisfy additional requirements. If the additional requirements are not completed, you will encounter a site inaccessible browser error.
- The Web Admin service may fail to stop. To resolve this issue, terminate
the
tomcat10.exeprocess. - If you do not update the SSL/TLS certificate to one with a minimum key
length of 2048, you will get an error similar to
this:
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Tip: <HOME> refers to the MOVEit Automation directory that is
created during installation. For example, C:\Program
Files\MOVEit\
Prerequisite
The Web Admin SSL/TLS certificate key length must be at least 2048. For
information about updating your SSL/TLS certificate, see Update the MOVEit Automation Web
Admin SSL/TLS Certificate.
Note: MOVEit Automation autogenerated certificates during installation for version
2024.1 and later have a key length of 2048. Earlier versions, up to and
including version 2024.0 had a key length of 1024. If you upgrade to 2024.1 or
later, you must manually update the Web Admin SSL/TLS certificate.
To enable Web Admin FIPS-mode on new installs and upgrades (2024.1 and later)
- Stop MOVEit Automation Web Admin using Windows services.
- Navigate to the <HOME>\MOVEit Automation Web Admin\Tomcat\conf directory.
- Open the server.xml
in a text editor as an administrator.Note: To open the server.xml file as an administrator, open the text editor as an administrator and then open the server.xml file in the text editor.
- Edit the FIPSMode value to
on:
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" FIPSMode="on" - Navigate to the <HOME>\MOVEit Automation Web Admin\Tomcat\bin directory.
- Open an administrator command prompt window in this folder and run the
following
command:
openssl.exe fipsinstall -module "<HOME>\MOVEit Automation Web Admin\Tomcat\bin\fips.dll" -out "<HOME>\MOVEit Automation Web Admin\Tomcat\conf\fipsmodule.cnf"This creates a fipsmodule.cnf file in the Tomcat\conf directory.
Note: Ensure that the generatedfipsmodule.cnffile has file system permissions that allow access by the account under which the MOVEit Automation Web Admin service is running.If the service runs under a virtual account or non‑administrator account and does not have access to this file, Tomcat may fail to start when FIPS mode is enabled.
- To ensure that Tomcat is pointing to the required OpenSSL FIPS mode files, choose from the
following options to set the correct environment variables:
- To set the environment variables universally, in the administrator
command prompt window opened in step 6, run the following
commands:
SETX OPENSSL_MODULES /M "<HOME>\MOVEit Automation Web Admin\Tomcat\bin"SETX OPENSSL_CONF /M "<HOME>\MOVEit Automation Web Admin\Tomcat\conf\openssl.cnf"
- To set the environment variables to apply to this service alone, in the
administrator command prompt window opened in step 6, run the
following
command:
tomcat10.exe //US/MICAdmin ++Environment OPENSSL_MODULES="<HOME>\MOVEit Automation Web Admin\Tomcat\bin";OPENSSL_CONF="<HOME>\MOVEit Automation Web Admin\Tomcat\conf\openssl.cnf"Note: When updating the environment variables, you must not include a space after the semi-colon ;. Doing so will cause the process to silently fail.You must use absolute paths, relative paths will result in a failure.
You might see a permissions warning, which you can ignore.
- To set the environment variables universally, in the administrator
command prompt window opened in step 6, run the following
commands:
- Start MOVEit Automation Web Admin using Windows services.
To disable Web Admin FIPS-mode (2024.1 and later)
- Stop MOVEit Automation Web Admin using Windows services.
- Open the server.xml in a text editor as an administrator.
- Edit the FIPSMode value to
off:
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" FIPSMode="off" - Choose from the following options to delete the environment variables
depending on how the variables were created:
- If
SETXwas used to create the environment variables, delete the variables manually from the Windows environment. - If the
tomcat10.execommand was used to create the environment variables, open and administrator command prompt window in the Tomcat\conf directory and run the following command:tomcat10.exe //US/MICAdmin --Environment ""You might see a permissions warning, which you can ignore.
- If
- Start MOVEit Automation Web Admin using Windows services.
Note: The environment variables must be removed to disable FIPS
mode.