MidPoint 3.5.1 "Einstein" Update 1

Last modified 22 Apr 2024 12:47 +02:00

Release 3.5.1 is a twentieth midPoint release. It is the first maintenance update for 3.5.x version family code-named Einstein. The Einstein release family brings lots of features related to identity governance, self-registration and support for JSON/YAML. This maintenance update brings number of smaller improvements, fixes and stability enhancements.

Release date09 April 2017
Release type Maintenance release
End of support21 December 2018

Albert Einstein (1879 - 1955) was a German-born theoretical physicist. He developed the general theory of relativity, one of the most important theories of modern physics. Einstein's contributions revolutionized physics and also significantly influenced other fields of science. His revolutionary work changed our understanding of the universe.

Einstein's theory of relativity was an inspiration for midPoint relativistic algorithms in the early days of the midPoint project. However even this recent midPoint version is related to Einstein's work. Einstein revolutionized the concept of time and introduced the principle of spacetime. MidPoint 3.5 includes a mechanism to reconstruct a state of objects as they were in the past. Einstein's theories provided a fundamental foundation for significant part of moder physics. Similarly the concept of policy rules introduced in midPoint 3.5 provides a fundamental foundations of more refined governance and compliance that will come in the future. Older midPoint concepts such as the concept of assignment get a stronger role in midPoint 3.5. The concepts and theories that midPoint is based on were refined and unified in midPoint 3.5. Although some of the fundamental work in midPoint 3.5 is still partially hidden and it may be slightly difficult to fully understand, we are persuaded that midPoint 3.5 is a major milestone in the midPoint history.


Majority of the work on the Einstein 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 a great gratitude to all the people that contributed to the midPoint project.

We would also like to thank:

  • AMI Praha for feature funding and for their continuous support and contributions to the midPoint project.

  • Carlos Ferreira for a complete translation of midPoint to Portuguese language.

  • Symas Corporation for their contributions in the area of cloud identity management.

  • A scientific institution that chose to remain anonymous for funding new midPoint features.


midPoint 3.5 provides following features:

Changes with respect to version 3.5

  • Specification of mapping domain and range

  • Easy customization of basic look and feel (color, icon, system name)

  • CredSSP and Exchange PowerShell support in AD/LDAP connector.

  • Minor GUI improvements

Changes With Respect to Version 3.4.1

  • Role catalog

  • Role request based on shopping cart paradigm

  • JSON/YAML support

  • Object lifecycle property

  • Passive Attribute Caching (EXPERIMENTAL)

  • Deputy (ad-hoc privilege delegation)

  • Object history (time machine)

  • Interactive audit log viewer

  • Audit log indexing improvements

  • Assignment metadata

  • Basic role lifecycle management (role approvals)

  • Improved approval processes

  • Self-registration

  • E-mail based password reset

  • Experimental support for policy rules

  • Weak construction

  • Improvements to AD connector in multi-domain environment

  • Identity merge

  • Better control over administration GUI forms

  • MariaDB support

  • Configurable limitations of parallel execution of tasks

  • Various user interface improvements

  • Internal code cleanup

  • Documentation improvements

Java 7 environment is no longer supported.
XPath2 scripting is no longer supported.
CSVFile Connector (legacy) is deprecated.


Release 3.5.1 (Einstein) is intended for full production use in enterprise environments. All features are stable and well tested.


  • MidPoint 3.5.1 comes with a bundled LDAP-based eDirectory connector. This connector is stable, however it is not included in the normal midPoint support. Support for this connector has to be purchased separately.


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 this release. The version numbers in parentheses are the actual version numbers used for the tests. However it is very likely that midPoint will also work in similar environments. Also note that this list is not closed. MidPoint can be supported in almost any reasonably recent platform (please contact Evolveum for more details).


  • OpenJDK 8 (1.8.0_91, 1.8.0_111)

  • Sun/Oracle Java SE Runtime Environment 8 (1.8.0_45, 1.8.0_65, 1.8.0_74)

Java 8 only

MidPoint 3.5 is supported only on Java 8 platforms. MidPoint supported both Java 7 and Java 8 for several years. The support for Java 7 was deprecated in midPoint 3.4.1 and it was removed in midPoint 3.5. It is finally the time to abandon obsolete technology and to move on.

Web Containers

  • Apache Tomcat 8 (8.0.14, 8.0.20, 8.0.28, 8.0.30, 8.0.33, 8.5.4)

  • Apache Tomcat 7 (7.0.29, 7.0.30, 7.0.32, 7.0.47, 7.0.50, 7.0.69)

  • Sun/Oracle Glassfish 3 (3.1)

  • BEA/Oracle WebLogic (12c)


  • H2 (embedded, only recommended for demo deployments)

  • PostgreSQL (8.4.14, 9.1, 9.2, 9.3, 9.4, 9.4.5, 9.5, 9.5.1)

  • MariaDB (10.0.28)

  • Percona Server (5.7.15)

  • MySQL (5.6.26, 5.7)
    Supported MySQL version is 5.6.10 and above (with MySQL JDBC ConnectorJ 5.1.23 and above).
    MySQL in previous versions didn’t support dates/timestamps with more accurate than second fraction precision.

  • Oracle 11g (

  • Microsoft SQL Server (2008, 2008 R2, 2012, 2014)

Unsupported Platforms

Following list contains platforms that midPoint is known not to work due to various issues. As these platforms are obsolete and/or marginal we have no plans to support midPoint for these platforms.

  • Java 6

  • Java 7

  • Sun/Oracle GlassFish 2

  • Apache Tomcat 6


Upgrade from midPoint 3.0, 3.1, 3.1.1, 3.2, 3.3, 3.3.1, 3.4 and 3.4.1

Upgrade path from MidPoint 3.0 goes through midPoint 3.1, 3.1.1, 3.2, 3.3 and 3.4. Upgrade to midPoint 3.1 first (refer to the midPoint 3.1 release notes). Then upgrade from midPoint 3.1 to 3.1.1, from 3.1.1 to 3.2 then to 3.3, then to 3.4.1 and finally to 3.5.

Upgrade from midPoint 3.5

MidPoint 3.5 data model is backwards compatible with both midPoint 3.5. No special upgrade procedure is needed.

Upgrade from midPoint 3.4 and 3.4.1

MidPoint 3.5 data model is essentially backwards compatible with both midPoint 3.4 and midPoint 3.4.1. However as the data model was extended in 3.5 the database schema needs to be upgraded using the usual mechanism.

If you are using Quartz Scheduler JDBC job store (e.g. because of clustering), there is a minor thing to take care of: If possible, make sure that QRTZ_FIRED_TRIGGERS table is empty before the upgrade. (It is because a "not nullable" column was added to that table, so we have to make a little guess when filling-in values for it.) The table is actually empty most of the time; it supposedly contains records only during task starting and execution. So, before upgrading, please make sure no task is executing.

  1. The simplest way how to ensure emptiness of the table is correctly shutting down midPoint before upgrade.

  2. If that would not help (and there are still some records in QRTZ_FIRED_TRIGGERS table), you might try to suspend tasks before shutting down midPoint.

  3. If even that would not help, you can probably ignore the fact, and run the upgrade script nevertheless.

Also it is recommended to close (i.e. accept or reject) all open approval work items.

MidPoint 3.5 is a release that fixes some issues of previous versions. Therefore there are some changes that are not strictly backward compatible.

  • Java 7 environment is no longer supported. Please upgrade to Java 8 before upgrading midPoint.

  • XPath2 scripting is no longer supported. Please migrate your XPath2 scripts to Groovy, JavaScript or Python.

  • Version numbers of the bundled connectors have changed (LDAP, AD and CSVfile connectors). Therefore connector references from the resource definitions that are using the bundled connectors need to be updated.

  • The PolicyViolationException was moved from com.evolveum.midpoint.model.api.PolicyViolationException to com.evolveum.midpoint.util.exception.PolicyViolationException. MidPoint source code is, of course, updated. But if you use this exception in the customization scripts and expressions you have to update the package name during the upgrade process.

Changes in initial objects since 3.4 and 3.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 following list and assess the impact on case-by-case basis:

  • 040-role-enduser.xml: fixed permissions

  • 043-role-delegator.xml: new file, role for delegators (deputy support)

  • 100-report-reconciliation.xml: fixed report

  • 110-report-user-list.xml: report fix for CSV output

  • 200-lookup-languages.xml: new supported languages

  • 210-lookup-locales.xml: new supported locales

  • 230-lookup-lifecycle-state.xml: new file, lookup for lifecycle states

Bundled connector changes since 3.4 and 3.4.1

  • The CSVFile Connector (legacy) is deprecated. It is still fully supported and it is still bundled with midPoint. However, it is technologically obsolete and it will be replaced by a new CSV Connector in midPoint 3.6. Therefore please consider using the new CSV Connector in new projects even with midPoint 3.5. The CSV Connector was not entirely finished at the time of midPoint 3.5 release - and that was the reason why midPoint 3.5 is still using the old connector. However it is expected that the new connector will be finished and stabilized in early 2017.

  • The LDAP connector was upgraded to the latest available version.

Behavior changes since 3.4 and 3.4.1

  • Attribute names are being escaped into XML element name form. All non-compliant characters are replaced by _xN sequence, where N is the hex representation of that particular character. E.g. a# becomes a_x23 and Parent Org Name becomes Parent_x20Org_x20Name. Please review your configuration files.

  • For repository searches, the only matching rule supported for plain string values is stringIgnoreCase. All the others will cause an exception to be thrown. (Previously they were silently ignored, which used to lead to hard-to-diagnose problems, e.g. if polyStringNorm was used instead.)

Public interface changes since 3.4 and 3.4.1

  • The PolicyViolationException was moved from com.evolveum.midpoint.model.api.PolicyViolationException to com.evolveum.midpoint.util.exception.PolicyViolationException.

Important internal changes since 3.4 and 3.4.1

These changes should not influence anyone using the midPoint. These changes should also not influence the XML-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.

  • The Prism data representation layer has been significantly re-engineered. This should not influence any midPoint usage. It also should not influence common customizations. However deep customizations and customizations that go beyond public APIs may need to be updated.

Known Issues

As all real-world software midPoint 3.5.1 has some known issues. 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 3.5.1 en masse. These issues will be fixed in future maintenance versions of midPoint only if the fix is requested by midPoint subscriber. No other issues will be fixed - except for severe security issues that may be found in the future.

The known issues of midPoint 3.5.1 may or may not be fixed in midPoint 3.6. 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 subscription. Or you can fix the bug yourself. MidPoint is always open to contributions.

This may seem a 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.

Was this page helpful?
Thanks for your feedback