<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title>Announcements and notices – Relution Customer Hub</title><subtitle>New and announced changes to Relution, one entry per announcement with its publication date.</subtitle><id>https://hub.relution.io/en/docs/product-info/announcements/</id><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/"/><link rel="self" type="application/atom+xml" href="https://hub.relution.io/en/docs/product-info/announcements/atom.xml"/><updated>2026-11-20T11:47:11+01:00</updated><author><name>Relution GmbH</name></author><entry><title>Infrastructure: Java for native installations</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#infrastructure"/><id>https://hub.relution.io/en/docs/product-info/announcements/#java-for-native-installations@2026-11-16</id><updated>2026-11-16T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Java for native installations:&lt;/strong&gt; Native Relution installations (without Docker) require &lt;em&gt;Java 21&lt;/em&gt; as of Relution &lt;strong&gt;26.0&lt;/strong&gt; and &lt;em&gt;Java 25&lt;/em&gt; as of Relution &lt;strong&gt;27.0&lt;/strong&gt;. With Java 21, Relution 27 does not run correctly; the log shows &lt;code&gt;java.lang.IncompatibleClassChangeError&lt;/code&gt;. Before updating to Relution 27, Java 25 is therefore installed and &lt;code&gt;JAVA_HOME&lt;/code&gt; is set to the new installation. Docker installations include the matching Java version in the image.&lt;/p&gt;</content></entry><entry><title>Relution Service: Update to 27.0.1</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#relution-service"/><id>https://hub.relution.io/en/docs/product-info/announcements/#update-to-2701@2026-10-29</id><updated>2026-10-29T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Update to 27.0.1:&lt;/strong&gt; Relution &lt;strong&gt;27.0.1&lt;/strong&gt; 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:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;API access tokens have a maximum lifetime of 1 year from creation; a shorter maximum lifetime can be set with &lt;code&gt;relution.security.access-token.max-lifetime&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;If the connection endpoint is changed in the OpenID Connect or system email configuration, the &lt;strong&gt;Client Secret&lt;/strong&gt; or &lt;strong&gt;Password&lt;/strong&gt; must be entered again; otherwise the configuration is not saved.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;The server retrieves the revocation list for Android attestation certificates from &lt;code&gt;android.googleapis.com&lt;/code&gt; once a day; with restricted internet access, this host must be allowed.&lt;/li&gt;
&lt;li&gt;When users are created via the REST API, the &lt;code&gt;hashedPassword&lt;/code&gt; field is ignored; the password is passed in the &lt;code&gt;password&lt;/code&gt; field.&lt;/li&gt;
&lt;/ul&gt;</content></entry><entry><title>Relution Service: HTTP Basic authentication disabled by default</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#relution-service"/><id>https://hub.relution.io/en/docs/product-info/announcements/#http-basic-authentication-disabled-by-default@2026-10-28</id><updated>2026-10-28T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;HTTP Basic authentication disabled by default:&lt;/strong&gt; Starting with Relution &lt;strong&gt;26.5.5&lt;/strong&gt;, the server no longer evaluates the &lt;code&gt;Authorization: Basic&lt;/code&gt; header 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 with &lt;code&gt;relution.security.basic-auth.enabled: true&lt;/code&gt; in &lt;code&gt;application.yml&lt;/code&gt;. More information is available at &lt;a href="https://hub.relution.io/en/docs/settings/rest-api/"&gt;REST API →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Relution Service: Text on wallpapers disabled by default</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#relution-service"/><id>https://hub.relution.io/en/docs/product-info/announcements/#text-on-wallpapers-disabled-by-default@2026-10-28</id><updated>2026-10-28T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Text on wallpapers disabled by default:&lt;/strong&gt; Starting with Relution &lt;strong&gt;26.5.5&lt;/strong&gt;, 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 &lt;code&gt;relution.wallpaper.text-rendering-enabled: true&lt;/code&gt; in &lt;code&gt;application.yml&lt;/code&gt;. As of Relution 27.0.2, text output is enabled by default again. More information is available at &lt;a href="https://hub.relution.io/en/docs/android-enterprise/policies/wallpaper/"&gt;Wallpaper →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Relution Service: Cluster: update all nodes together</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#relution-service"/><id>https://hub.relution.io/en/docs/product-info/announcements/#cluster-update-all-nodes-together@2026-10-28</id><updated>2026-10-28T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Cluster: update all nodes together:&lt;/strong&gt; Starting with Relution &lt;strong&gt;26.5.5&lt;/strong&gt;, 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 &lt;a href="https://hub.relution.io/en/docs/installation/installation/cluster_setup/"&gt;HA Cluster (Advanced) →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Infrastructure: Linux: file permissions of the installation directory</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#infrastructure"/><id>https://hub.relution.io/en/docs/product-info/announcements/#linux-file-permissions-of-the-installation-directory@2026-10-28</id><updated>2026-10-28T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Linux: file permissions of the installation directory:&lt;/strong&gt; Starting with Relution &lt;strong&gt;26.5.8&lt;/strong&gt;, Relution checks on startup whether the service user can write to the &lt;code&gt;portal/&lt;/code&gt;, &lt;code&gt;teacher/&lt;/code&gt;, &lt;code&gt;bin/&lt;/code&gt; or &lt;code&gt;lib/&lt;/code&gt; directories of the installation directory and reports this with one error message per directory (&lt;code&gt;Installation path … is writable for the user running Relution&lt;/code&gt;) in the log. This affects installations in which &lt;code&gt;/opt/relution&lt;/code&gt; is entirely owned by the service user via &lt;code&gt;chown -R relution:relution&lt;/code&gt;. Startup is not prevented. &lt;code&gt;root&lt;/code&gt; is recommended as the owner of the installation directory; only &lt;code&gt;log/&lt;/code&gt; and &lt;code&gt;branding/&lt;/code&gt; remain writable for the service user. More information is available at &lt;a href="https://hub.relution.io/en/docs/installation/after-installation/update/"&gt;Update →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Secure Mail Gateway: Secure Mail Gateway 26.0.7: configuration required for private IP addresses</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#secure-mail-gateway"/><id>https://hub.relution.io/en/docs/product-info/announcements/#secure-mail-gateway-2607-configuration-required-for-private-ip-addresses@2026-10-23</id><updated>2026-10-23T00:00:00+02:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Secure Mail Gateway 26.0.7: configuration required for private IP addresses:&lt;/strong&gt; Starting with SMG &lt;strong&gt;26.0.7&lt;/strong&gt;, 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 &lt;code&gt;allowed-targets&lt;/code&gt; in &lt;code&gt;application.yaml&lt;/code&gt; — otherwise ActiveSync requests are no longer forwarded to the Exchange server. More information and configuration examples are available at &lt;a href="https://hub.relution.io/en/docs/installation/installation/smg-standalone/#forwarding-to-private-ip-addresses"&gt;Forwarding to private IP addresses →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Relution Service: API access tokens: mandatory expiration</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#relution-service"/><id>https://hub.relution.io/en/docs/product-info/announcements/#api-access-tokens-mandatory-expiration@2026-10-22</id><updated>2026-10-22T00:00:00+02:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;API access tokens: mandatory expiration:&lt;/strong&gt; Starting with Relution &lt;strong&gt;26.5.5&lt;/strong&gt;, API access tokens always have an expiration date (default: 30 days); extending the expiration date is no longer possible. &lt;strong&gt;Existing tokens without an expiration date expire 30 days after the update&lt;/strong&gt; 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 &lt;strong&gt;26.5.7&lt;/strong&gt;, 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 &lt;a href="https://hub.relution.io/en/docs/settings/rest-api/"&gt;REST API →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Relution Service: Update to 26.4.0+</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#relution-service"/><id>https://hub.relution.io/en/docs/product-info/announcements/#update-to-2640@2026-08-19</id><updated>2026-08-19T00:00:00+02:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Update to 26.4.0+:&lt;/strong&gt; With Relution &lt;strong&gt;26.4.0&lt;/strong&gt;, 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 &lt;code&gt;Access is forbidden&lt;/code&gt; (&lt;code&gt;TLS required&lt;/code&gt; in the server log). In this case, the configuration must be adjusted according to the steps described in &lt;a href="https://hub.relution.io/en/docs/installation/knowledge-base/login-tls-reverseproxy/"&gt;Login: Access is forbidden →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Relution Service: Update to 26.1+</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#relution-service"/><id>https://hub.relution.io/en/docs/product-info/announcements/#update-to-261@2026-07-31</id><updated>2026-07-31T00:00:00+02:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Update to 26.1+:&lt;/strong&gt; Before upgrading to version 26.1 or higher, a &lt;strong&gt;26.0.x&lt;/strong&gt; 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 &lt;a href="https://hub.relution.io/en/docs/installation/knowledge-base/update261/"&gt;Permission denied after update to 26.1 →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Infrastructure: New base image: Ubuntu instead of AlmaLinux</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#infrastructure"/><id>https://hub.relution.io/en/docs/product-info/announcements/#new-base-image-ubuntu-instead-of-almalinux@2026-07-31</id><updated>2026-07-31T00:00:00+02:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;New base image: Ubuntu instead of AlmaLinux&lt;/strong&gt;: Starting with Relution &lt;strong&gt;26.4.0&lt;/strong&gt;, the Relution container image is based on Ubuntu instead of AlmaLinux.&lt;/p&gt;</content></entry><entry><title>Secure Mail Gateway: Secure Mail Gateway</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#secure-mail-gateway"/><id>https://hub.relution.io/en/docs/product-info/announcements/#secure-mail-gateway@2026-06-18</id><updated>2026-06-18T00:00:00+02:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Secure Mail Gateway:&lt;/strong&gt; Starting with Relution &lt;strong&gt;26.4.0&lt;/strong&gt;, using the Secure Mail Gateway feature requires a dedicated standalone service. Without it the feature is no longer available. In &lt;strong&gt;26.3&lt;/strong&gt;, the new mode can be activated optionally using a feature toggle. More information and migration guidance are available at &lt;a href="https://hub.relution.io/en/docs/installation/installation/smg-standalone/"&gt;Installing Secure Mail Gateway →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Storage: Object Storage</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#storage"/><id>https://hub.relution.io/en/docs/product-info/announcements/#object-storage@2026-01-21</id><updated>2026-01-21T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Object Storage:&lt;/strong&gt; 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 &lt;a href="https://hub.relution.io/en/docs/installation/object-storage/migration/"&gt;Migration from MinIO to SeaweedFS →&lt;/a&gt;.&lt;/p&gt;</content></entry><entry><title>Relution Service: Device groups</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#relution-service"/><id>https://hub.relution.io/en/docs/product-info/announcements/#device-groups@2025-12-17</id><updated>2025-12-17T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;Device groups:&lt;/strong&gt; As announced, Relution &lt;strong&gt;26.0&lt;/strong&gt; 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.&lt;/p&gt;</content></entry><entry><title>Storage: MariaDB</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#storage"/><id>https://hub.relution.io/en/docs/product-info/announcements/#mariadb@2025-12-17</id><updated>2025-12-17T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;MariaDB:&lt;/strong&gt; Relution requires &lt;em&gt;MariaDB 10.11 or higher&lt;/em&gt;. &lt;em&gt;Support for MariaDB is only available until the end of 2027.&lt;/em&gt;&lt;/p&gt;</content></entry><entry><title>Storage: PostgreSQL</title><link rel="alternate" type="text/html" href="https://hub.relution.io/en/docs/product-info/announcements/#storage"/><id>https://hub.relution.io/en/docs/product-info/announcements/#postgresql@2025-12-17</id><updated>2025-12-17T00:00:00+01:00</updated><content type="html">&lt;p&gt;&lt;strong&gt;PostgreSQL:&lt;/strong&gt; Relution requires &lt;em&gt;PostgreSQL 14 or higher&lt;/em&gt;. Using &lt;em&gt;PostgreSQL 18&lt;/em&gt; is recommended.&lt;/p&gt;</content></entry></feed>