Supported Platforms & Requirements
Deployment Options
-
Linux Package
-
Docker Compose
-
Kubernetes
Supported Operating Systems for Linux Packages
MTG provides linux packages for the following operating systems:
-
Ubuntu 22.04
-
Ubuntu 24.04
-
SUSE Linux 15.5
-
SUSE Linux 15.6
-
Redhat Enterprise Linux (RHEL) 8.10
-
Redhat Enterprise Linux (RHEL) 9.x
More details and installation instructions can be found here.
Docker Compose
Installations in docker environments are supported using MTG docker images and a custom MTG docker compose file. Instructions can be found here.
Kubernetes
Kubernetes (K8s) Specific Requirements
-
Kubernetes version: v1.24.0 or higher
-
Tools:
helmandkubectlmust be installed -
Permissions: Sufficient privileges to deploy Helm resources on the cluster
Instructions can be found here.
Software Access and Delivery
Requirements differ depending on the chosen deployment method.
-
For Docker and Kubernetes deployments, access to the MTG Docker Registry is mandatory.
-
For Linux package-based deployments, installation packages are available via our linux package repository or through manual downloads from the Download Center.
MTG Docker Registry Access (Docker and Kubernetes only)
-
Network access to
repo.mtg.deand public image registries is required to pull container images. -
Credentials (username/password) are required for authentication.
-
Access should be validated by successfully pulling test images, such as:
-
mtg-clm-ui:4.1.0 -
kms-ui:3.3.0
-
Linux Package Access
For Linux package-based deployments, installation packages can be obtained through two supported channels:
-
MTG Linux Package Repository Recommended for standard installations where internet access is available.
-
MTG Download Center Provides manual package downloads. This method is particularly useful in air-gapped or restricted environments.
Component Compatibility
The following versions were tested with MTG CLM 6.17.0, as documented in the 6.17.0 release notes. For another CLM release, use that release’s compatibility requirements and migration instructions.
| Component | Version |
|---|---|
Java |
25 |
Keycloak |
26.8.1 |
MariaDB |
11.4 |
PostgreSQL |
16 or 18 |
Oracle Database |
19.3 |
MTG CARA |
3.8.0 |
Databases
Choose one of the database versions listed above. Docker Compose deployments support MariaDB or PostgreSQL; the Docker Compose distribution must also support the selected database version. TIP: See MariaDB Galera Cluster Configuration Guide.
Upgrade Requirements
-
CLM 6.11.0 and later require Java 25. See Java Runtime Migration.
-
CLM 6.7.0 and later require MariaDB 11.4 when using MariaDB. Earlier CLM releases require MariaDB 10.6.
-
Before upgrading to CLM 6.16.0 or later, first run a release from 6.4.0 through 6.15.0 and successfully complete its migration and initialization steps.
-
When choosing an intermediate release, skip CLM 6.7.0 and 6.8.0; use 6.8.1 or later instead.
-
Installations earlier than CLM 4.4.0 also need an intermediate update to a release from 4.4.0 through 6.4.0 before using Keycloak 26.4.0 or later.
Check the release notes for each intermediate release before updating its dependencies. The current compatibility table does not apply to every step of an upgrade from an older release.
Hardware Security Modules
MTG ERS can integrate with various Hardware Security Modules (HSMs) for secure key management.
Supported HSMs
The following HSM systems are officially supported:
-
Securosys HSMs
-
Utimaco Security Server, CryptoServer SeGen 2, and CSe series
-
Thales Luna HSMs compatible with Luna 10.x Universal Client
-
Nitrokey HSM 2
-
nCipher nShield Connect XC2
Third Party Components
Keycloak
Keycloak is an open source software product that allows single sign-on with identity and access management aimed at modern applications and services.
Use the Keycloak version listed in the component compatibility table for CLM 6.17.0. For older CLM releases, consult their release notes before updating Keycloak.
General Network Requirements
To ensure proper operation of MTG ERS, all servers involved in the deployment must meet the following network requirements:
-
Inter-server connectivity: All servers must be able to communicate with each other over the relevant ports, including:
-
HTTP/HTTPS for application communication
-
Database ports for the chosen DBMS
-
HSM ports if a Hardware Security Module is used
-
-
DNS resolution: All servers must be able to resolve the DNS names of all nodes in the deployment, as well as their own hostname.
-
Firewall and routing: Ensure that any firewalls, security groups, or routing policies allow the above traffic during both installation and normal operation.
Optional MTG Engineer Support for Initial Setup
MTG offers an optional service where our engineers can assist with the initial deployment of MTG ERS.
Access Requirements (if support is requested)
To ensure a smooth setup, MTG engineers require temporary access to the systems being installed:
-
SSH access (preferred) to all target servers or nodes, with credentials or key-based authentication provided in advance.
-
Sufficient user privileges to perform installation and configuration tasks (e.g., root or sudo access).
-
Network access to internal services, databases, HSMs, and other infrastructure components.
-
Access to any required configuration files or secrets in advance (e.g., database credentials, PKCS#11 libraries).