Version 1.12.x#

This page shows the changelog for Nubus for Kubernetes 1.12.x:

Version 1.12.0 - 2025-07-31#

This is the sixteenth production release of Nubus for Kubernetes.

Upgrade path

For the upgrade to version 1.12.0, your deployment must run on version 1.11.0 to 1.11.2. For the general steps to upgrade an existing Nubus for Kubernetes deployment, see Upgrade in Univention Nubus for Kubernetes - Operation Manual [1].

Migration steps#

This section lists necessary migration steps that may apply to you. You need to run them before the upgrade.

  1. Operators that have enabled the 2FA Helpdesk before this release need to perform the following steps:

    1. Visit Keycloak Admin Console and switch to the Nubus realm.

    2. Navigate to Client Scopes in the sidebar.

    3. Select twofa-default and open the Mappers tab.

    4. Open the groups-mapper entry.

    5. Set Full group path to off and save the changes.

    See also

    Keycloak Admin Console

    in Univention Nubus for Kubernetes - Operation Manual [1] for information about where to find the Keycloak Admin Console.

  2. Operators that have configured the pullPolicy for the 2FA Helpdesk container images need to adjust the following variables:

Changes#

This section lists the changes in 1.12.0 grouped by component in Nubus for Kubernetes.

Portal Service#

  • Fix Portal frontend integration with the Intercom Service. Nubus for Kubernetes only loads the Intercom Service silent login and the news feed after user sign-in.

  • Add feature toggle nubusPortalServer.portalServer.featureToggles.api_me in the Portal Server to deactivate enrichment of user information in the Portal Frontend, such as display name. The activated API me feature can cause longer sign-in times.

  • Add feature flag in the Portal Frontend to improve the accessibility of lists. You can toggle it through the nubusPortalServer.portalServer.featureToggles.native_html_list Helm Chart value. The default value is false and deactivates the feature.

    Operators that activate the toggle, need to review their custom CSS selectors for the Portal theme and verify if the custom theme still produces the expected results. For more information, see Customization of portal theme.

  • Portal HTML content in tooltips and notifications is now sanitized to prevent XSS vulnerabilities.

Keycloak#

  • Update Keycloak to version 26.3.1, which includes security fixes for CVE-2025-7365 and CVE-2025-7784.

  • Keycloak now runs with a read-only file-system.

2FA Helpdesk#

Provisioning Service#

SCIM#

  • SCIM Server now restarts if the ConfigMap changes.

  • Fix SCIM user’s name formatting which caused None to be part of the generated user’s name if display name wasn’t present.

  • Rename SCIM Provisioning to SCIM Client.

  • SCIM wait for Keycloak no longer needs the /admin endpoint to be available.

  • SCIM Server allows unsetting of extended attributes.

Management UI#

  • You can hide potentially sensitive data in the UMC’s meta.json file using the experimental UCR variable global.configUcr.umc.web.meta.hide-sensible-data. Additionally, meta.json file no longer includes the server’s address by default. It’s now only visible during system setup.

  • Fix UMC ingress annotations that prevented the UMC deployment with nginx-ingress controller 1.12 and later.

LDAP directory service#

Fix LDAP Secondary configuration that prevented the component from scaling more than 8 replicas.

Others#

Update all components in Nubus for Kubernetes to use the UCS 5.2-2 base image and include bug fixes up to UCS 5.2 erratum 130. For UCS errata updates, see Security and bugfix errata for UCS 5.2. Reference date is 26. June 2025.

  • You can configure the primary groups for users and computers at the parent container objects where Nubus creates an object.

  • You can now deactivate the default global search container, that is All containers, through the UCR variable global.configUcr.directory.manager.web.modules.search.default-search. If deactivated, you can enable the UCR variable global.configUcr.directory.manager.web.modules.search.default-search to limit searches to module-specific default containers. This improves search performance and result relevance, especially in large environments with many objects.