Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

In Progress

This release is under development. Therefore the information presented here is incomplete and inaccurate.
For information regarding the latest stable release please see Release 2.1

Crius

Release 2.2 is a eight midPoint release code-named Crius. The Crius release brings new feature ....

Planned release date: Spring 2013

Features

midPoint 2.2 provides following features:

Changes with respect to version 2.1.x

  • Change to Apache License version 2.0
  • Multi-layer attribute access limitations
  • Fetch strategy in schema handling to support attributes that are not returned from connector by default
  • Redesigned activation support with richer set of activation states and mappings
  • Support easy activation existence mappings (e.g. easy configuration of "disables instead of delete" feature)
  • Support for user validity time constraints (valid from, valid to)
  • Support for resource validity time constrains (valid from, valid to)
  • Introducing concept of inducement as a generalization of the user-account assignment concept
  • More expression variables to support complex RBAC assignment/inducement structures and dynamic roles

Quality

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

Platforms

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 contant Evolveum for more details).

Java

  • Sun/Oracle Java SE Runtime Environment 6 update 26 or above (1.6.0_26, 1.6.0_35 64bit, 1.6.0_37)
  • Sun/Oracle Java SE Runtime Environment 7 (1.7.0_09)

Web Containers

  • Apache Tomcat 6 (6.0.32, 6.0.33)
  • Apache Tomcat 7 (7.0.30, 7.0.32)
  • Sun/Oracle Glassfish 3 (3.1)

Databases

  • H2 (embedded, only recommended for demo deployments)
  • PostgreSQL (8.4.14, 9.1, 9.2)
  • MySQL
    Supported MySQL version is 5.6.4 and above (still unreleased) and MySQL JDBC ConnectorJ 5.1.23).
    MySQL in previous versions didn't support dates/timestamps with second fraction precision. Tested with version MySQL 5.6.9.rc and ConnectorJ 5.1.23.
  • Oracle 11g (11.2.0.2.0)

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.

  • Sun/Oracle Java SE Runtime Environment 6 update 25 or older
  • Sun/Oracle GlassFish 2

Download and Install

Background and History

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, etc.

For the full project background see the midPoint History page.

Known Issues

  1. Consistency mechanism fails to operate correctly in case new user is added (under some cirmustances) (https://jira.evolveum.com/browse/MID-1056)
  2. Provisioning script arguments can only be static (https://jira.evolveum.com/browse/MID-1194)
  3. Policy changes require application server restart in some scenarios (https://jira.evolveum.com/browse/MID-1187)
  4. Export creates data that do not comply to schema in some situations. Workaround: turn off schema checking during reimport. (https://jira.evolveum.com/browse/MID-1197)
  5. Import falsely displays a referential error in some cases (https://jira.evolveum.com/browse/MID-1198)
  6. Reimport of deep organizational structure may fail to create proper structure (https://jira.evolveum.com/browse/MID-1199)
  7. Use of consistency mechanism may cause application of a value of a weak mapping even if it should not be applied under some circumstances (https://jira.evolveum.com/browse/MID-1201)

See Also

  • No labels