Security Compliance

'Wijmo license in this application is invalid / trial.' pop-up in ARM Cockpit web client 2025.4.1

In Access Rights Manager (ARM) 2025.4.1, the ARM web interface / Cockpit displays a pop-up stating that the Wijmo license is invalid or in trial when managing users, groups, or starting a new recertification campaign, even though your ARM license is valid. This is a known configuration issue with the embedded Wijmo component. The error is cosmetic regarding the ARM license and is resolved by upgrading to the fixed ARM release.

First published date

1/29/2026 6:41 PM

Last published date

2/26/2026 12:43 AM

Overview

This article applies to environments where the ARM web client (Cockpit) shows a Wijmo license warning even though the ARM license itself is properly installed and valid.

Observed Symptoms:

  • When using the ARM web interface / Cockpit to manage users and groups, a pop-up appears stating that the Wijmo license is invalid or in trial.

  • The pop-up may occur intermittently or repeatedly while working in the ARM web client.

  • The same message can appear when starting a new recertification in ARM.

  • Your ARM product license is valid, but the message raises concerns about licensing and future functionality.

  • Functionality generally continues to work, but the repeated pop-ups are disruptive and lead to confusion about license status.

This affects ARM 2025.4.1, while the major ARM 2025.4 release does not exhibit this behavior.

Product section

Access Rights Manager

Cause

  • This is a known issue in ARM 2025.4.1 and is limited to this version.

  • The root cause is a configuration error related to the embedded Wijmo license used by the ARM web client (Cockpit).

  • In the ARM 2025.4.1, the Wijmo component is deployed with an incorrect/invalid license configuration, causing the web UI to report the Wijmo license as invalid or trial, even though the overall ARM license is valid.

Resolution

This issue is limited to ARM 2025.4.1. A fix has already been implemented and is included in ARM 2025.4.2. Consider upgrading your environment, as upgrading to this version will fully resolve the issue.