Release 4.2 is a thirty-third midPoint release code-named Maxwell. The 4.2 release brings new reporting mechanism, updates to auditing implementation, continued improvement for authentication and handful of other interesting improvements. Most importantly, midPoint 4.2 brings experimental updates to the very foundations of midPoint.

Release date: 23rd October 2020
Release type: Feature release
End of support: 23rd October 2021

James Clerk Maxwell (1831 - 1879) was a Scottish scientist in the field of mathematical physics. He is best known for Maxwell equations that form a foundation of classical electromagnetism, classical optics and electric circuits. The equations are part of a theory of electromagnetic radiation, bringing together for the first time theories of electricity, magnetism and light. Maxwell's work was theoretical, but it has profound effect on both theoretical and practical parts of science and engineering. Maxwell has described the path that we follow up to this day.

Similarly to Maxwell's theories, midPoint 4.2 lays down theoretical foundations with significant potential for the future. Most of them are results of midPrivacy initiative. Axiom is a new modeling language that works on conceptual levels to provide support for metadata schemas. Axiom was used to implement data provenance functionality deep in midPoint core data layers. The insights that originated from the provenance effort inspired fundamental improvements in processing of midPoint mappings. Overall, the work on midPoint 4.2 provided a lot of inspiration and theoretical foundations for the future. MidPoint code is almost a decade old. The Maxwell release builds up essential theories that would allow midPoint to flourish for decades to come.


Majority of the work on the Maxwell release was done by the Evolveum team. However, this release would not be possible without the help of our partners, customers, contributors, friends and families. We would like to express our thanks to all the people that contributed to the midPoint project both by providing financial support, their own time or those that maintain a pleasant and creative environment for midPoint team. However, midPoint project would not exist without proper funding. Therefore we would like to express our deepest gratitude to all midPoint subscribers that made midPoint project possible.


There are too many features in midPoint 4.2 to list them in details. The Features page lists the features of most recent midPoint release.

Changes with respect to version 4.1

New Features and Improvements

Deprecation, Feature Removal And Incompatible Changes

Releases Of Other Components

Purpose and Quality

Release 4.2 (Maxwell) is intended for full production use. It is a feature release, supported only for a reduced time period. Therefore it is intended for users that prefer new features over long-term stability.

All features are stable and well tested - except the features that are explicitly marked as experimental or partially implemented. Those features are supported only with special subscription contract.


Following list provides summary of limitation of this midPoint release.

This list is just an overview and it may not be complete. Please see the documentation regarding detailed limitations of individual features.


MidPoint is known to work well in the following deployment environment. The following list is list of tested platforms, i.e. platforms that midPoint team or reliable partners personally tested with this release. The version numbers in parentheses are the actual version numbers used for the tests.

It is very likely that midPoint will also work in similar environments. But only the versions specified below are supported as part of midPoint subscription and support programs - unless a different version is explicitly agreed in the contract.

Support for some platforms is marked as "deprecated". Support for such deprecated versions can be removed in any midPoint release. Please migrate from deprecated platforms as soon as possible.


OpenJDK 11 is a recommended Java platform to run midPoint.

Support for Oracle builds of JDK is provided only for the period in which Oracle provides public support (free updates) for their builds. As far as we are aware, free updates for Oracle JDK 11 are no longer available. Which means that Oracle JDK 11 is not supported for MidPoint any more. MidPoint is an open source project, and as such it relies on open source components. We cannot provide support for platform that do not have public updates as we would not have access to those updates and therefore we cannot reproduce and fix issues. Use of open source OpenJDK builds with public support is recommended instead of proprietary builds.

Web Containers

MidPoint is bundled with an embedded web container. This is the default and recommended deployment option. See Stand-Alone Deployment for more details.

Apache Tomcat is supported as the only web container for midPoint. Support for no other web container is planned. Following Apache Tomcat versions are supported:

Apache Tomcat 8.0.x and 8.5.x are no longer supported.

Explicit deployment to an external web container was supported since the beginning of midPoint. That was the usual practice at the time when midPoint started. But that was some time ago and the world is a different place now. MidPoint supports stand-alone deployment model for several years. It is now the default and recommended deployment model. It works very well and it simplifies a lot of things. Therefore in order to simplify midPoint maintenance and support we are deprecating the explicit deployment model. Support for explicit deployment will be removed soon. Stand-alone deployment will be the only supported option in the future.


MidPoint supports several databases. However, performance characteristics and even some implementation details can change from database to database. Since midPoint 4.0, PostgreSQL is the recommended database for midPoint deployments.

Our strategy is to officially support the latest stable version of PostgreSQL database (to the practically possible extent). PostgreSQL database is the only database with clear long-term support plan in midPoint. We make no commitments for future support of any other database engines. See Repository Database Support page for the details.

Only a direct connection from midPoint to the database engine is supported. Database and/or SQL proxies, database load balancers or any other devices (e.g. firewalls) that alter the communication are not supported.

Supported Browsers

Any recent version of the browsers is supported. That means any stable stock version of the browser released in the last two years. We formally support only stock, non-customized versions of the browsers without any extensions or other add-ons. According to the experience most extensions should work fine with midPoint. However, it is not possible to test midPoint with all of them and support all of them. Therefore, if you chose to use extensions or customize the browser in any non-standard way you are doing that on your own risk. We reserve the right not to support customized web browsers.

Microsoft Internet Explorer compatibility mode is not supported.

Important Bundled Components

Tomcat9.0.37Web container
ConnId1.5.0.17ConnId Connector Framework
LDAP connector bundle3.1LDAP, Active Directory and eDirectory connector
CSV connector2.4Connector for CSV files
DatabaseTable connector1.4.4.0Connector for simple database tables

Download And Install

Release Form


Install Instructions


Installing midPoint 4.2


From Git repository (tag "v4.2")

Building MidPoint From Source Code

Java API [JAR]

Schema Doc [ZIP]


MidPoint is software that is designed for easy upgradeability. We do our best to maintain strong backward compatibility of midPoint data model, configuration and system behavior. However, midPoint is also very flexible and comprehensive software system with a very rich data model. It is not humanly possible to test all the potential upgrade paths and scenarios. Also some changes in midPoint behavior are inevitable to maintain midPoint development pace. Therefore we can assure reliable midPoint upgrades only for midPoint subscribers. This section provides overall overview of the changes and upgrade procedures. Although we try to our best it is not possible to foresee all possible uses of midPoint. Therefore the information provided in this section are for information purposes only without any guarantees of completeness. In case of any doubts about upgrade or behavior changes please use services associated with midPoint subscription or purchase professional services.

Upgrade From MidPoint 4.1.x

MidPoint 4.2 data model is not completely backwards compatible with previous midPoint versions. However, vast majority of data items is compatible. Therefore the usual upgrade mechanism can be used. There are some important changes to keep in mind:

Upgrade From MidPoint 4.0.x Or Older

Upgrade from midPoint 4.0.x or older is not supported directly. Please upgrade to midPoint 4.1.x first.

Changes In Initial Objects Since 4.1

MidPoint has a built-in set of "initial objects" that it will automatically create in the database if they are not present. This includes vital objects for the system to be configured (e.g. role Superuser and user administrator). These objects may change in some midPoint releases. But to be conservative and to avoid configuration overwrite midPoint does not overwrite existing objects when they are already in the database. This may result in upgrade problems if the existing object contains configuration that is no longer supported in a new version. Therefore the following list contains a summary of changes to the initial objects in this midPoint release. The complete new set of initial objects is in the config/initial-objects directory in both the source and binary distributions. Although any problems caused by the change in initial objects is unlikely to occur, the implementors are advised to review the changes and assess the impact on case-by-case basis.

There were numerour changes to initial objects in this release. Please review source code history for list of changes.

Bundled Connector Changes Since 4.1

Behavior Changes Since 4.1

Old channel namespace (4.1 and earlier)New channel namespace (4.2 and later)

Channel URI migration

In order to facilitate migration of channel URIs, some of them are migrated automatically (see MID-6547):

  1. Channel URIs in tasks. These are automatically migrated when the task is run for the first time under midPoint 4.2.
  2. Channel URIs in object, assignment, and credentials metadata (metadata.createChannel). This property is automatically migrated when the object, assignment, or credentials metadata is updated for the first time under midPoint 4.2.
  3. Channel URIs in serialized model operation context, e.g. in approval cases. These are not migrated in the repository, but de-serialized into new form when model operation context is read from the repository.

The following channel URIs are not migrated automatically, because they are part of the configuration:

  1. channel and exceptChannel properties in mappings,
  2. channel in synchronization reaction definition (in synchronization  section of resource definition),
  3. channels in flexible authentication configuration.

The following channel URIs are also not migrated automatically:

  1. channel information in the audit log. However, audit log viewer in midPoint GUI was modified to be able to filter on both old and new channel URIs;
  2. channel in shadow synchronization situation description,
  3. channel in task "actions executed" statistics,
  4. channel in operation execution records.

We assume that channel information under points 2-4 above is not used for any automated processing. If you need to migrate these, you can write e.g. your own bulk action that will do so.

Public Interface Changes Since 4.1

Important Internal Changes Since 4.1

These changes should not influence people that use midPoint "as is". These changes should also not influence the XML/JSON/YAML-based customizations or scripting expressions that rely just on the provided library classes. These changes will influence midPoint forks and deployments that are heavily customized using the Java components.

Known Issues and Limitations

As all real-world software midPoint 4.2 has some known issues. Full list of the issues is maintained in jira. As far as we know at the time of the release there was no known critical or security issue.

There is currently no plan to fix the known issues of midPoint 4.2 en masse. These issues will be fixed in future maintenance versions of midPoint only if the fix is covered by a support agreement or subscription. No other issues will be fixed - except for severe security issues that may be found in the future.

The known issues of midPoint 4.2 may or may not be fixed in following maintenance releases or in midPoint 4.3. This depends on the available time, issue severity and many variables that are currently difficult to predict. The only reliable way how to make sure that an issue is fixed is to purchase midPoint support. Or you can fix the bug yourself. MidPoint is always open to contributions.

This may seem a little bit harsh at a first sight. But there are very good reasons for this policy. And in fact it is no worse than what you get with most commercial software. We are just saying that with plain language instead of scrambling it into a legal mumbo-jumbo.

Some of the known issues are listed below:


Planned release dates are just that: they are planned. We do not promise or guarantee release dates. Software development is a creative activity that includes a lot of inherent risk. We are trying really hard to provide the best estimates. We are not able to provide precise dates for releases or deliveries. Do not rely on midPoint release dates. Plan your project properly to address the risk of delayed midPoint releases.

Planned scope of midPoint releases is also an estimate. MidPoint development process always includes the balancing of the iron triangle. Therefore planned release scope may change at any time. There is a method to make sure that midPoint releases will work well for your project and that method is platform subscription.

We do not make any claims that midPoint is perfect. Quite the contrary. MidPoint is a practical software, developed by living and breathing developers and deployed in a real world. There are both known and unknown issues in midPoint. Also, midPoint is not feature-complete. New features are introduced in midPoint all the time. But not all of them are completed. There are always some limitations. As the license states, midPoint is provided "AS IS". Please do not rely on midPoint functionality that you have not tested to make sure that it works. MidPoint support and subscription programs are a way how to handle those issues. But even with support service, do not rely on functionality that is not documented. If you plan to use undocumented or non-existing functionality, platform subscription is the right service for you.

See Also