Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Release 3.7.2 is a twenty fifth midPoint release. It is the second maintenance update for 3.7.x version family code-named Darwin. The 3.7.2 release brings bugfixes and several minor improvements.

Planned release Release date: 8th June 2018

titleCharles Darwin

Charles Darwin (1809 - 1882) was English naturalist, geologist and biologist, best known for the theory of evolution. Darwin's famous book On the Origin of Species described theory of evolution, mechanism of natural selection that explains the diversity of life. His voyage on HMS Beagle established him as an eminent geologist and made him famous as a popular author. Darwin has been described as one of the most influential figures in human history.

Darwin's theory of evolution is the unifying theory of the life sciences. The theory describes the process how species evolve and adapt over successive generations. MidPoint 3.7 is such an evolutionary step in midPoint development. This midPoint release brings gradual improvements in many diverse areas. Identity governance features are improved, both in capabilities of the engine and the user interface. MidPoint expressions have gained more power and ease of use. There are notable improvements in user interface, security, task management and many smaller improvements in various areas. The scope of almost the entire release was guided by midPoint subscribers and sponsors - which provided the perfect environment for this step in midPoint evolution.


Table of Contents


Majority of the work on the Darwin 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.


midPoint 3.7.2 provides following features:

Changes with respect to version 3.7.1

  • Support for CredSSP version 5 and 6.
  • Various bugfixes
  • Ninja tool ready for upgrade to midPoint 3.8

Old CSVFile Connector is deprecated and it is no longer bundled with midPoint.
Support for PostgreSQL 8.4 is deprecated. The support will be dropped in the future.
Oracle database 11g support was deprecated in midPoint 3.7. This will be replaced for Oracle 12c database support in midPoint 3.8.
Suport for MySQL 5.6 is deprecated.
Support for Microsoft SQL Server 2008, 2008 R2 and 2012 is deprecated. The support will be dropped in the future.


Release 3.7.2 (Darwin) is intended for full production use in enterprise environments. 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 and/or professional services contract.


  • MidPoint 3.7.2 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 with 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, 1.8.0_151)
  • Sun/Oracle Java SE Runtime Environment 8 (1.8.0_45, 1.8.0_65, 1.8.0_74, 1.8.0_131)

Web Containers

  • Apache Tomcat 8 (8.0.14, 8.0.20, 8.0.28, 8.0.30, 8.0.33, 8.5.4)
  • BEA/Oracle WebLogic (12c) - (warning) special subscription required


titleWeb container (application server) support

Currently there are no plans to remove support for deployed midPoint installation using a WAR file. However, it is possible that this deployment form will get phased out eventually unless there are active subscribers preferring this deployment method. MidPoint subscription is strongly recommended if you plan to use this method in the future.


  • H2 (embedded). Supported only in embedded mode. Not supported for production deployments. Only the version specifically bundled with midPoint is supported.
    H2 is intended only for development, demo and similar use cases. It is not supported for any production use. Also, upgrade of deployments based on H2 database are not supported.
  • PostgreSQL (8.4.14, 9.1, 9.2, 9.3, 9.4, 9.4.5, 9.5, 9.5.1)
    Support for PostgreSQL 8.4 is deprecated. The support will be dropped in the future.
  • MariaDB (10.0.28)
  • MySQL (5.6.26, 5.7)
    Support for MySQL version is 5.6.x is deprecated.
  • Oracle 11g (
    Oracle 11g support is deprecated in midPoint 3.7. This will be replaced for Oracle 12c support in midPoint 3.8.
  • Microsoft SQL Server (2008, 2008 R2, 2012, 2014)
    Support for Microsoft SQL Server 2008, 2008 R2 and 2012 is deprecated. The support will be dropped in the future.

Supported Browsers

  • Firefox (any recent version)
  • Safari (any recent version)
  • Chrome (any recent version)
  • Opera (any recent version)
  • Microsoft Internet Explorer (version 9 or later)


Microsoft Internet Explorer compatibility mode is not supported.

Important Bundled Components

ConnId1.4.3.0ConnId Connector Framework
LDAP connector bundle1.6LDAP, Active Directory and eDirectory connector
CSV connector2.1Connector for CSV files
DatabaseTable connector1.4.2.0Connector for simple database tables

Download and Install

titleStand-alone deployment model

MidPoint 3.7 and 3.7.2 deployment method has changed. Stand-alone deployment is now the default deployment method. MidPoint default configuration, scripts and almost everything else was adapted for this method.


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 3.0, 3.1, 3.1.1, 3.2, 3.3, 3.3.1, 3.4, 3.4.1, 3.5, 3.5.1, 3.6, 3.6.1 and 3.7

Upgrade path from MidPoint 3.0 goes through midPoint 3.1, 3.1.1, 3.2, 3.3, 3.4.1, 3.5.1 and 3.6.1. 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, 3.5.1, 3.6.1 and finally to 3.7.2.

Upgrade from midPoint 3.7 and 3.7.1

MidPoint 3.7.2 data model have not changed since midPoint 3.7. Therefore there is no need to update the database.

Changes in initial objects since 3.7 and 3.7.1

There were no changes to initial object since midPoint 3.7.

Bundled connector changes since 3.7 and 3.7.1.

LDAP and AD connectors were upgraded to latest versions.

Behavior changes since 3.7

  • URLs used by Stand-Alone Deployment were changed to match the URLs used by Tomcat-based deployments of midPoint 3.6 and earlier. This means that all deployment forms now use /midpoint/ context root path in the URL by default (e.g. http://localhost:8080/midpoint/). This choice was made based on user feedback to keep the compatibility with previous midPoint versions and to keep the two deployment models as closely aligned as possible. For the stand-alone deployment there is an automatic HTTP redirect from the root URL (e.g. http://localhost:8080/) to midPoint context root (e.g. http://localhost:8080/midpoint/). Therefore in midPoint 3.7.2 both deployment method should behave in a natural, expected and compatible way.
  • Processing of authorizations for proxy authentication in the REST interface was corrected. The processing of proxy authorizations now behave as documented.
  • Processing of object authorizations was corrected. Authorizations now take into consideration also the properties of existing removed containers even in replace and id-only delete cases. Therefore, appropriate property authorization is needed even when deleting a value that contains those properties.
  • Password reset schema was deprecated. Existing password reset configuration still works, but it will be replace by new password reset configuration in the future.

Public interface changes since 3.7

  • REST interface was extended with experimental password reset method.

Important internal changes since 3.7

There were not critical internal changes since midPoint 3.7.

Known Issues and Limitations

There is a support to set up storage of credentials in either encrypted or hashed form. There is also unsupported and undocumented option to turn off credential storage. This option partially works, but there may be side effects and interactions. This option is not fully supported yet. Do not use it or use it only at your own risk. It is not included in any midPoint support agreement.


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.

See Also