Announcements and notices
Relution Service
- Update to 27.0.1: Relution 27.0.1 is based directly on 26.5.8 and contains all changes up to and including 26.5.8. In addition, the following applies as of Relution 27.0.1:
- API access tokens have a maximum lifetime of 1 year from creation; a shorter maximum lifetime can be set with
relution.security.access-token.max-lifetime. - If the connection endpoint is changed in the OpenID Connect or system email configuration, the Client Secret or Password must be entered again; otherwise the configuration is not saved.
- For account-based user enrollment of Apple devices, the sign-in to Relution is valid only once and for a limited time; enrollments not yet completed at the time of the update are restarted.
- The server retrieves the revocation list for Android attestation certificates from
android.googleapis.comonce a day; with restricted internet access, this host must be allowed. - When users are created via the REST API, the
hashedPasswordfield is ignored; the password is passed in thepasswordfield.
- API access tokens have a maximum lifetime of 1 year from creation; a shorter maximum lifetime can be set with
- API access tokens: mandatory expiration: Starting with Relution 26.5.5, API access tokens always have an expiration date (default: 30 days); extending the expiration date is no longer possible. Existing tokens without an expiration date expire 30 days after the update and must be replaced with new tokens before then. Exception for PostgreSQL: when updating to 26.5.5 or 26.5.6, such tokens expired immediately there. Starting with Relution 26.5.7, the 30-day period also applies to PostgreSQL; tokens that have already expired remain expired and must be replaced with new tokens. More information about API access tokens is available at REST API →.
- HTTP Basic authentication disabled by default: Starting with Relution 26.5.5, the server no longer evaluates the
Authorization: Basicheader by default. Scripts and monitoring queries that log in with a user name and password (e.g. Prometheus) must be switched to API access tokens. As a temporary measure, Basic Auth can be re-enabled withrelution.security.basic-auth.enabled: trueinapplication.yml. More information is available at REST API →. - Text on wallpapers disabled by default: Starting with Relution 26.5.5, the text stored in a wallpaper configuration is no longer applied to the image by default; devices on all platforms receive the image without text. The portal still shows the text field. If required, text output can be re-enabled with
relution.wallpaper.text-rendering-enabled: trueinapplication.yml. As of Relution 27.0.2, text output is enabled by default again. More information is available at Wallpaper →. - Cluster: update all nodes together: Starting with Relution 26.5.5, communication between the cluster nodes is encrypted and authenticated. Nodes running a version before 26.5.5 cannot communicate with nodes running 26.5.5 or later. An update across this version boundary is therefore applied to all nodes together rather than node by node during operation. The key is generated automatically on first start; no configuration is required. More information is available at HA Cluster (Advanced) →.
- Update to 26.4.0+: With Relution 26.4.0, the internal application server was switched from Undertow to Tomcat. If the reverse proxy runs on a different server than Relution itself, logging in may subsequently fail with the message
Access is forbidden(TLS requiredin the server log). In this case, the configuration must be adjusted according to the steps described in Login: Access is forbidden →. - Update to 26.1+: Before upgrading to version 26.1 or higher, a 26.0.x version must be installed and started at least once. If any 26.0.x version is already running, updating to 26.0.3 specifically is not required. Background: Relution 26.1 only supports database upgrades from version 26.0, so a 26.0.x version is required as an intermediate step. Additionally, updating to 26.1 may cause the Docker container to fail to start due to a permission issue on the temp directory. The solution is described in Permission denied after update to 26.1 →.
- Device groups: As announced, Relution 26.0 automatically migrates organisations to device groups. Support for the legacy functionality is removed. This version also drops rule sets, which have been replaced by device group actions.
Secure Mail Gateway
- Secure Mail Gateway 26.0.7: configuration required for private IP addresses: Starting with SMG 26.0.7, the Secure Mail Gateway blocks forwarding to non-public addresses by default. If the Exchange server resolves to a private IP address (e.g. 10/8, 172.16/12, 192.168/16), that address or address range must be allowed as a target under
allowed-targetsinapplication.yaml— otherwise ActiveSync requests are no longer forwarded to the Exchange server. More information and configuration examples are available at Forwarding to private IP addresses →. - Secure Mail Gateway: Starting with Relution 26.4.0, using the Secure Mail Gateway feature requires a dedicated standalone service. Without it the feature is no longer available. In 26.3, the new mode can be activated optionally using a feature toggle. More information and migration guidance are available at Installing Secure Mail Gateway →.
Storage
- Object Storage: For installations using MinIO as the local S3-compatible storage provider, a migration to SeaweedFS is recommended, because MinIO has ceased development. A guide for this is available at Migration from MinIO to SeaweedFS →.
- MariaDB: Relution requires MariaDB 10.11 or higher. Support for MariaDB is only available until the end of 2027.
- PostgreSQL: Relution requires PostgreSQL 14 or higher. Using PostgreSQL 18 is recommended.
Infrastructure
- Java for native installations: Native Relution installations (without Docker) require Java 21 as of Relution 26.0 and Java 25 as of Relution 27.0. With Java 21, Relution 27 does not run correctly; the log shows
java.lang.IncompatibleClassChangeError. Before updating to Relution 27, Java 25 is therefore installed andJAVA_HOMEis set to the new installation. Docker installations include the matching Java version in the image. - Linux: file permissions of the installation directory: Starting with Relution 26.5.8, Relution checks on startup whether the service user can write to the
portal/,teacher/,bin/orlib/directories of the installation directory and reports this with one error message per directory (Installation path … is writable for the user running Relution) in the log. This affects installations in which/opt/relutionis entirely owned by the service user viachown -R relution:relution. Startup is not prevented.rootis recommended as the owner of the installation directory; onlylog/andbranding/remain writable for the service user. More information is available at Update →. - New base image: Ubuntu instead of AlmaLinux: Starting with Relution 26.4.0, the Relution container image is based on Ubuntu instead of AlmaLinux.
Note: Software in End-Of-Life (EOL)
For security reasons, Relution does not support software that has reached its end of life (EOL), since no further security patches are provided.
New handbook articles
An overview of new features in recent Relution versions, linking to the corresponding handbook articles.
Version 26.5
On Premises Installation
- Relution Shield (Add-on) → Set up a technical user and create an API access token
- Server-Side Encryption (SSE-C)
General
- Dashboard
- Teacher → Web links and browsing restrictions
- Advanced placeholders → User certificates
- Profile for ADE → Minimum OS version
Apple macOS
Education
Android Enterprise
Settings
- Certificate Pool
- TLS Trust Configuration → Certificate pinning (Apple enrollment)
- Meta Organizations
- OIDC with Entra → Redirect URI for device enrollment
- Relution as Identity Provider
- OIDC with Workspace → Redirect URI for device enrollment
Version 26.4
On Premises Installation
General
Apple iOS
Apple macOS
Windows
Settings
- Global Organization → Organization switcher
- TLS Trust Configuration
- OIDC with Entra → Add redirection URI
- OIDC with Workspace → Scoped redirect URIs
Version 26.3
On Premises Installation
- Installing Secure Mail Gateway → Feature toggle for on-premise installations (26.3)
- APNS Push Certificates → Migration from the Previous Process