Release 2.2.1 is a ninth midPoint release. It is also the first maintenance update for 2.2.x version family code-named Crius. The Crius release brings numerous new features and many improvements.
Release date: January 28th 2014
midPoint 2.2.1 provides following features:
Release 2.2.1 (Crius Update 1) is intended for full production use in enterprise environments. All features are stable and well tested.
MidPoint is known to work well in the following deployment environments. The following list is list of tested platforms, i.e. platforms on which 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 on almost any reasonably recent platform (please contact Evolveum for more details).
Please note that Java 6 environment is no longer supported (although it might work in some situations).
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.
midPoint is roughly based on OpenIDM version 1. When compared to OpenIDM v1, midPoint code was made significantly "lighter" and provides much more sophisticated features. Although the architectural outline of OpenIDM v1 is still guiding the development of midPoint almost all the OpenIDM v1 code was rewritten. MidPoint is now based on relative changes and contains advanced identity management mechanisms such as advanced RBAC, provisioning consistency and other advanced IDM features. MidPoint development is independent for more than two years. The development pace is very rapid. Development team is small, flexible and very efficient. Contributions are welcome.
For the full project background see the midPoint History page.
Extra values in tolerant multi-value attributes with high-order dependencies . Workaround: set the attribute to non-tolerant.