Release Notes

2026-07

Not deployed / Deployed in staging / Deployed In Prod

2026.07.01 - My-Identity

AWS-Paris AWS-dublin S3NS

This release introduces new capabilities on SAP integration, role request and bug fixes

Delivery Timeline

  • Staging:

  • Production:


New Features

Feature name: Native SAP Authorization Model Discovery (Composite Roles, Standard Roles, Transactions)

Key benefit:

  • Native discovery of the SAP authorization model (composite roles, standard roles, transactions) directly within Memority

  • No more need to manually recreate SAP roles in Memority

  • Centralized visualization of SAP information directly from the Memority interface

  • Ability to generate reports (e.g. number of users per transaction)

  • Upcoming enhancement: Segregation of Duties (SoD) management at the transaction level

Read more: https://doc.memority.eu/configuration-guide/latest/sap-replication-task-definition https://doc.memority.eu/configuration-guide/latest/sap-transaction-connector https://doc.memority.eu/configuration-guide/latest/sap-role-connector


Feature name: SAP GRC Integration via new Workflow capabilities (Retryable Script Task)

Key benefit:

  • Native workflow step (Script Task) capable of triggering external calls (e.g. to SAP GRC) directly from a Memority workflow

  • Built-in retry mechanism with configurable timeout — no need for custom scripting to handle transient failures

  • Workflow pauses natively until SAP GRC validation is received, before deciding whether the role is granted (or not) in Memority

  • Fully auditable: each call, retry attempt, and validation outcome is traceable within the workflow history (API_WORKFLOW_HISTORY)

Read more: https://doc.memority.eu/configuration-guide/latest/workflow


Feature name: Import Simulation Report

Key benefit:

  • Provides a detailed view of the impacts of an import before final validation

  • Gives precise details of the actions that would be triggered if thresholds are reached

  • Reduces the risk of errors or side effects during mass imports

  • Facilitates business/technical validation before triggering


Feature name: Hourly Granularity for Role Request

Key benefit:

  • Allows role request screens to be configured with hourly granularity instead of the default daily granularity

  • Enables granting entitlements over a much shorter time window

  • Strengthens the least-privilege principle by limiting the exposure duration of sensitive access

  • Addresses use cases requiring very short-term temporary access (e.g. one-off intervention, on-call duty)

Read more: https://doc.memority.eu/configuration-guide/latest/roles-widgets


Feature name: Multiple Instances of the Same Role in a Single Request

Key benefit:

  • Allows the same role to be requested multiple times within a single request

  • Particularly useful for assigning a role across two different scopes with different effective dates

  • Avoids having to trigger the request process multiple times for the same role

  • Simplifies the user experience


Bug Fixes

  • Fixed a bug affecting exports on the reporting side

  • Security fixes


2026.07.01 - Presets 3.3.0

This release introduces a new way to manage dimensions for applications' provisioning

Delivery Timeline

  • Production:


New Features

Applications Dimensions

Manage application entitlements (profiles, groups and licenses) as native Memority entries and reuse them consistently in provisioning rights and applicative roles.

  • Create and maintain a catalog of Profiles, Groups and Licenses for each application

  • Right templates for application-specific provisioning rights

Read More: Application Dimensions


Bug Fixes

  • Added missing translations for self-role features

2026.07.16 - Presets 3.4.0

This release introduces built-in Segregation of Duties (SoD) management in Memority presets along with categorization capabilities for roles and applications.

Delivery Timeline

  • Production:


New Features

Segregation of Duties

You can now create and manage SoD rules directly from the user portal. This allows you to define four types of SoD rules :

  • Role to role

  • Application to application

  • Roles category to roles category

  • Applications category to applications category

Categories for Roles and Applications

Roles and applications can now be organized into categories. Those are used to define SoD rules at the category level, but can be used for other general purposes.

2026.07.21 - IntelliJ MIT Plugin 2.5.1

This release extends the compatibility of MIT plugin to IntelliJ 2026.2.

Delivery Timeline

  • JetBrains MarketPlace:


New Feature

  • MIT is now available for IntelliJ 2026.2


Bug Fixes

  • Multiple bug fixes


2026.07.28 - My-Identity


AWS-Paris AWS-dublin S3NS

This release introduces new capabilities on configuration and bug fixes

Delivery Timeline

  • Staging:

  • Production:


New Features

Feature name: SAP Replication configuration by UI

Key benefit:

  • Simplifying configuration through the UI

Read more: https://doc.memority.eu/configuration-guide/latest/sap-replication-task-definition https://doc.memority.eu/configuration-guide/latest/sap-transaction-connector https://doc.memority.eu/configuration-guide/latest/sap-role-connector


Feature name: Native Named Loggers in Groovy Scripts

Key benefit:

  • Native addition of named loggers across all Groovy scripts, automatically scoped to the object in which the script is positioned

  • Enables clearer, better-organized logs — no need to manually tag or structure log output per script

  • Significantly simplifies debugging by allowing integrators to quickly identify which object/script a given log line originates from

  • Primarily targeted at integrators, accelerating troubleshooting and, in turn, the delivery of advanced functionality



Bug Fixes

  • Fixed a bug affecting application portal when application has a bad format url (query param without value)

  • Added new context to Groovy scripts to encode a payload

  • Fixed SoD validation message during multi role request assignment

  • Fixed a bug related to attribute deletion when it's used in a Groovy script

  • Security fixes