Relution Server 26.2

Important note regarding the update: If you are currently using an older version, we recommend that you first update to version 26.0.3 and then to version 26.2.

OneRoster Integration

Relution 26.2 expands the platform with a standards-based integration for the OneRoster API. This allows school administrative data to be connected in a structured manner and automatically synchronized with Relution.

The following data types are supported:

• Users: Students and teachers
• Organizations: Schools and organizational units to be mapped in Relution
• Classes: School classes and groups that are synchronized as Relution courses

In Relution, the configuration is done under Settings → OneRoster. There, you can set up a connection to a OneRoster-compatible system (e.g., Untis). The configuration includes, among other things, the server URL, login credentials, and optional mapping settings for assigning organizational units.

A test connection and a preview of the imported data are available for setup. This allows you to validate the structure and scope of classes, courses, teachers, and students in advance. The subsequent synchronization run creates or updates the corresponding objects in Relution.

This integration significantly reduces the amount of manual maintenance required in school environments, as user and class structures are imported directly from the source system and kept in sync.

External URL Management in Global Server Settings

With this release, the external server URL can be managed directly via the user interface in Relution’s global server settings. Previously, this was only possible via the application.yml file. With the new feature, authorized users with the “Manage External URL” permission can now view, edit, and save the URL.

The existing configuration is loaded from application.yml at startup and pre-filled. Additionally, a validation check is performed to ensure that only valid HTTPS URLs can be saved. This eliminates the need for static configuration files, and the external URL can be flexibly maintained directly within the system.

Improved Version History

The version history has been expanded and now provides a visual representation of changes:

• Green: added
• Red: removed
• Orange: modified
• Strikethrough: disabled

Even complex changes (e.g., new UUIDs) are displayed in a clear and traceable manner. Direct navigation between versions facilitates comparison and increases transparency in complex configurations.

Improved Management of Native Apps

With this release, Relution optimizes the management of native Android apps. Installation statuses are now tracked more reliably, allowing for more targeted control of app deployments. Apps that are already installed are detected, preventing unnecessary reinstallations.

If a user deletes an app configured as non-removable, Relution automatically triggers a reinstallation. The system also checks whether an installation is required for new assignments or updates.

The result is more stable and efficient app distribution with reduced device load.

Support for Credential Providers

With version 26.2, Relution expands its support for Android Enterprise to include the configuration of credential providers. A credential provider is an app or service that provides login credentials for other applications, such as an authenticator app like Microsoft Authenticator.

Starting with Android 14, administrators can specify which apps on the device are allowed to be used as credential providers. This behavior can be controlled either centrally via policies or on an app-specific basis via managed app policies.

Additionally, you can specify for each app whether it is allowed to act as a credential provider. This enables a fixed assignment of a provider to an application. This gives organizations granular control over which applications are allowed to manage passwords, passkeys, and other login credentials.

Default App Settings

With version 26.2, default apps can be defined centrally, e.g., for browsers, phone calls, SMS, Wallet, Assistant, or Launcher. A prioritized list can be stored for each application type. The first compatible and installed app is automatically set as the default.

Note: Once an application type is configured, users can no longer set their own default apps. Availability depends on the Android version and enrollment type.

New Policy: Device Radio State Control (DeviceRadioState)

The new DeviceRadioState policy enables centralized control of wireless connections on Android Enterprise devices.

Supported features include:

• Wi-Fi status (Android 13 and later)
• Airplane mode
• Ultra-Wideband (Android 14 and later)
• Disable 2G cellular (Android 14 and later)
• Minimum Wi-Fi security level
• eSIM settings

This allows you, for example, to disable insecure connections or selectively restrict communication interfaces.

Retrieve and Display Windows Update Status

Relution enhances transparency for Windows updates. Using the Windows Companion, you can centrally retrieve and display the update status of devices.

The “Fetch and display Windows Update status” feature actively retrieves update data from the device. The information displayed includes the title, description, category, download status, and whether the update is mandatory.

This new section provides a centralized overview and lays the foundation for future enhancements in update management.

Data Roaming Control for iOS

With Relution 26.2, administrators can centrally manage data roaming settings on iOS devices. A new device action allows administrators to selectively enable or disable data roaming, for example, to avoid unexpected charges while abroad.

You can find the release changelog here.

For the sake of readability, the masculine form is used on this page for personal pronouns and personal nouns. In the spirit of equal treatment, these terms apply to all genders. The use of the masculine form is purely for editorial reasons and does not imply any judgment.