Key new capabilities
-
Identity & security
-
Keycloak is now supported as an identity provider for both cloud and on‑prem deployments, extending SSO and user management integration options (setup requires consultation).
-
-
Accessibility & input hardware
-
Adds support for the ANKER EAA‑Pad as an accessibility device, broadening supported accessible usage scenarios on kiosks. See EAA Checklist for Accessible Kiosk Design
-
-
Power and device management
-
Supports Nexmosphere NEO for power management, enabling more advanced use cases where display power supply and device control are relevant (e.g., turning peripherals on/off).
-
Platform and editor updates
-
Editor fixes
-
Fixes issues in the project editor when handling .webp and .gif images, improving reliability for asset-heavy layouts.
-
-
Runtime stack refresh
-
Updates the client platform to Electron 40.5.0 with Chromium 144.0.7559.177, giving a more current browser engine for stability, security, and compatibility in continuous operation. [144 is a January 2026 stable and extended‑stable branch (now also LTC/LTS in some ChromeOS channels).
-
-
General stability
-
Includes additional unspecified bug fixes and optimizations across the platform.
-
Practical implications
-
Better fit into enterprise IAM stacks (via Keycloak) in both cloud and on‑prem kiosk/signage environments.
-
Stronger accessibility story at the hardware level (EAA‑Pad) on top of the earlier accessibility features introduced in 1.7–1.8.
-
Improved options for interactive retail or DOOH scenarios where power control and sensor-driven experiences via Nexmosphere gear matter.
-
Reduced risk from an aging embedded Chromium and fewer editor hiccups with modern image formats.
Definitions
-
Keycloak is an open‑source identity and access management (IAM) platform used to handle authentication, single sign‑on, and authorization for applications and APIs.
Core idea
-
Runs as a central identity provider (IdP) that apps trust for login, logout, and token issuance instead of each app managing its own accounts.
What it provides
-
Single sign‑on and single logout across multiple web, mobile, and backend apps using OpenID Connect and SAML.
-
User management, roles, and groups, including integration with LDAP/Active Directory or external IdPs (Google, Azure AD, etc.).
-
Identity brokering and federation so you can plug multiple identity sources into one consistent login experience.
In kiosk/digital signage terms, it’s the central SSO service your players, CMS, and admin portals can delegate login to, instead of each system rolling its own auth.
-