Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -345,7 +345,7 @@ You can use the **Search** field to search for a specific action by name.

This tab contains a list of actions that were archived after the period specified in the **Log Settings** tab has expired. You can download the archive if required for auditing purposes.

##### Log Settings
##### Log Settings {#log-settings}

You can select how long the actions are kept in the logs, in days. The minimum number of days is 1, and the maximum is 365. You can also specify the logging level, from no logging to complete logging.

Expand Down
93 changes: 93 additions & 0 deletions content/en/docs/releasenotes/private-platform/2/2.8.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,99 @@ These release notes cover changes made to the [Private Mendix Platform](/private
This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version release. Customers are encouraged to upgrade to this version. [Previous MTS versions](/releasenotes/private-platform/1-13/) of Private Mendix Platform are no longer supported.
{{% /alert %}}

## 2.8.2

### Release date: November 20, 2026

Version 2.8.2 of Private Mendix Platform introduces a number of improvements, updates, and fixes.

#### Improvements

##### Marketplace Enhancements

Marketplace content can now be managed by a team rather than a single content owner. Marketplace content management is now included in the existing Dynamic Role Management functionality. You can use group membership and resource roles to grant granular permissions for editing component settings and uploading new items.

##### Inherited Resources Labeled in Group Management

The **Group Management** page now displays labels to clearly indicate which apps and Marketplace content items were inherited from a child group.

##### Platform and Resource Role Assignment for OIDC Users

We have added the option to dynamically assign Platform Roles and Resource Roles to users based on OIDC token claims, enabling zero-touch user provisioning without manual role assignment after SSO login.

##### Logout Confirmation Message

To comply with AWS ISV attestation requirements, when logging out of Private Mendix Platform, users now see a message confirming that they have logged out.

##### Activity Log Enhancements

On the [Log Settings](/private-mendix-platform/reference-guide/admin/company/#log-settings) page, you can now select Azure Blob Storage as an external backup target. Azure Blob Storage supports both managed identity and static credentials.

#### Updates

##### Studio Pro Updates

* Studio Pro 9.24 LTS latest patch version updated to [9.24.44](/releasenotes/studio-pro/9.24/#92444)
* Studio Pro 10.24 LTS latest patch version updated to [10.24.28](/releasenotes/studio-pro/10.24/#102428)
* Studio Pro 11.6 MTS latest patch version updated to [11.6.10](/releasenotes/studio-pro/11.6/#11610)
* Studio Pro 11.12 MTS latest patch version updated to [11.12.6](/releasenotes/studio-pro/11.12/#11126)

##### Other Platform Components {#example}

* Mendix Operator version [2.29.0](/releasenotes/developer-portal/mendix-for-private-cloud/#2.29.0)
* Private Cloud License Manager (PCLM) version 0.11.3
* Interactor v1.25.8
* Interactor Bridge v1.24.8
* Collector v1.23.10
* Authenticator v1.19.6
* Maia Appgen 0.39.5
* Maia LLM Gateway 0.15.6
* PDF Docgen v1.0.5

#### Fixes

* (API) When creating an environment through API, you can now specify the required environment ID. (Ticket 291228)
* (API) The app owner and their Owner role can no longer be removed through API. (Ticket 283910)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should not be write it as something like:

We have fixed an issue where the app owner and their Owner role can no longer be removed through API.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understand it correctly, the app owner and role could previously be removed through API, and that was not the desired behaviour. The fix prevents this from happening.

* (API) We have resolved some User API validation issues.
* (API) We have fixed an issue where Deploy pipelines with manual approval steps would not run correctly when triggered through API.
* (API) We have fixed an issue where some API requests would result in incorrect response codes.
* (API) We have fixed an issue with the Group API, where updating the parent group through the API did not work correctly.
* (Marketplace) We have fixed an issue where it was possible to select an empty group when transferring a content item.
* (Marketplace) We have fixed an issue where downloading contents uploaded through a Marketplace bundle would not overwrite the current version of the content, and would add it as a new widget instead. (Ticket 286141)
* (General) We have updated the supported versions of Grafana and Loki. (Ticket 291148)
* (General) We have added the option to enable the secret store for custom environment variables, custom JVM options, and custom Jetty options. (Ticket 291073)
Comment thread
katarzyna-koltun-mx marked this conversation as resolved.
Resolved
* (General) We have fixed an issue where constant values were not saved in the Key Vault. (Ticket 290997)
* (General) We have clarified some messages displayed in the UI when updating constant values with a secret store enabled. (Ticket 290482)
* (General) We have fixed an issue where a blank option was displayed in the **Secret Store Type** dropdown. (Ticket 290090)
* (General) We have fixed an issue where the Debugger password was encoded twice. (Tickets 289313, 289613)
* (General) We have fixed an issue where randomly-generated Debugger passwords sometimes did not fulfill the requirements. (Ticket 285508)
* (General) We have fixed an issue where it was possible to submit an Admin password change more than once. (Ticket 283650)
* (General) We have fixed an issue where the **Resource Role** dropdown was incorrectly labeled **Platform Role**. (Ticket 287020)
* (General) The option to select **Automatic (Azure Key Vault Only)** in the **Secret Store Type** dropdown is now disabled for cluster types other than **AKS**.
* (General) We have fixed an issue where no error message was shown when saving a secret without the `Key Vault write` permission.
* (General) Selecting the **Store to Secret Manager** option now prevents the creation Constant and Runtime Setting names with characters that are not accepted by the Secret Manager.
* (General) We have fixed an issue where it was possible to copy the Debugger password more than once.
* (General) We have fixed an issue where claim values were not validated correctly.
* (General) We have fixed an issue with OIDC claim mapping, where users were not added to groups correctly.
* (General) We have resolved an issue where the UI did not show that a pod was restarting after an admin password change.
* (General) We have resolved an issue where importing an app with the **Import App** function would show an error about group ownership.
* (General) We have resolved an issue where an app imported with the **Import App** function would not appear in the **My Apps > Direct access** section of the home page.
* (General) We have resolved an issue where logs and events were not visible with Azure Monitor selected as a data source for logs.
* (General) We have fixed an issue where the Build pod `git` step would fail on Azure DevOps Servers.
* (General) We have fixed an issue where the graph on the **Platform Statistics** page was zoomed in.
* (General) We have fixed some CVEs related to the following:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of mentioning that we fixed CVEs, we can write something like:

We have updated PMP and its associated component to their latest dependency versions in order to improve security score ratings for container images.


* `GHSA-j92g-9f8w-j867+postgresql-42.7.11.jar`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my view, we should not specify the cves here.
Want to also know the view from Meng

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mengdix Can you comment on this? We have listed specific CVEs in previous release notes.

* `CVE-2025-27818+kafka-streams-2.7.2.jar`
* `CVE-2025-27818+kafka-log4j-appender-2.4.1.jar`
* `CVE-2025-27819+kafka-streams-2.7.2.jar`
* `CVE-2026-34480+org.apache.logging.log4j.log4j-api-2.17.2.jar`
* `CVE-2025-27819+kafka-log4j-appender-2.4.1.jar`
* `CVE-2026-9538+perl-Archive-Tar`
* `CVE-2026-42496+perl-Archive-Tar`

#### Known Issues

## 2.8.1

### Release date: September 25, 2026
Expand Down
Loading