Page tree

Versions Compared

Key

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

...

Warning
titleIn Progress

This release is planned. Therefore the information presented here is incomplete and inaccurate.
For information regarding the latest stable release please see Release 4.0

Gutenberg Update 1

Release 4.0.1 is a twenty eight nineht midPoint release. It is the fist maintenance update for 4.0.x version family code-named code-named Gutenberg. The 4.0 release in a major milestone in midPoint development. It brings long-awaited features such as archetypes and support for multiple equivalent accounts. Many internal mechanisms were significantly improved. There is also a number of exciting experimental features. However, perhaps the most important aspect of midPoint 4.0 is the .x is a long-term support (LTS). Gutenberg will be supported for many years to come. version family. The 4.0.1 release brings bugfixes and minor improvements.

Planned release date: October 2019

...

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

Changes with respect to version 4.0

New Features, Improvements and Bugfixes

  • Archetype assignments are always active, regardless of the lifecycle state.
  • TODO

Deprecation, Feature Removal And Incompatible Changes

  • Support for eDirectory was removed. eDirectory support was a maintenance burden. There is currently no subscriber using eDirectory connector, therefore the code of eDirectory connector was removed from the LDAP connector bundle.
  • Support for BEA/Oracle WebLogic deployment was removed. Weblogic support was maintained because of a special arrangements with one of the first midPoint subscribers. Weblogic support is not needed by that subscriber and it is not used by any other subscriber. Therefore support for Weblogic deployment is no longer available. Tomcat is not the only supported web container. Support for any other containers is not planned.

Changes with respect to version 3.9

New Features and Improvements

  • Major features
  • User interface improvements
    • Object Collections and Views
    • Sections (virtual containers) in object details
    • Dashboards and status reports (experimental)
    • Shopping cart improvements
    • Reworked "projections" tab
    • Ability to set custom name for midPoint
    • Case management improvements (experimental)
    • Session management page
    • Minor user experience improvements
  • Provisioning
    • Support for PolyStrings all the way to the connector (experimental)
    • Asynchronous (messaging) connector options (prototype)
    • Improved shadow consistency with primaryIdentifierValue property
    • Support for seach hierarchy scope

  • Miscellaneous improvements
    • Mapping range pre-defined sets
    • Mapping state properties
    • Support for populate expressions in autoassignments
    • Task management in cluster is using REST
    • Autogenerated node identifier in a cluster
    • Support for attachments in mail notifications
    • Whitelists for notifications
    • Support for expression in mapping time constraints
    • Partial support for polystring "lang" and translations (experimental)
    • Miscellaneous clustering improvements
    • Many improvements in reconciliation and synchronization tasks
  • Internals
    • Improved Prism API and code structure
    • Improved GUI interfaces and code structure
    • Long-term support stabilization
    • Java 11 support
    • New internal engine for policy-based approvals (replaces Activiti BPM)
    • Cluster management is using REST instead of JMX
    • Numerous performance and scalability improvements

Deprecation, Feature Removal And Incompatible Changes

  • Support for Java 8 is deprecated. Running midPoint on OpenJDK 8 is supported for midPoint 4.0 and the preliminary plan is to support for the usual lifetime of ordinary support of midPoint 4.0.x line (which means 3 years). But Java 8 support may be shortened, e.g. in case that Oracle or OpenJDK project will stop providing updates to Java 8 platform. It is strongly recommended to upgrade to Java 11 as soon as possible.
  • Support for Oracle Java builds is limited (see below).
  • Support for PostgreSQL 9.5 (9.5, 9.5.1) is deprecated.

  • Support for Microsoft SQL Server 2014 is deprecated.

  • SOAP-based IDM Model Web Service Interface is deprecated. It will no longer be maintained and it will be completely removed in future versions. Please use RESTful interface instead.
  • As SOAP interface is deprecated, the example SOAP client (model-client component) was removed from midPoint source code. It will no longer be maintained.
  • There are many schema changes, including many incompatible schema changes. Please see the upgrade section below for the details.
  • Activiti BPM that was used as "workflow engine" was removed from midPoint.
  • Support for BEA/Oracle WebLogic (12c) is deprecated and it is no longer available as a public feature. Artifacts for weblogic support will be removed as soon as such action is confirmed with the affected subscribers.eDirectory was removed. eDirectory support was a maintenance burden. There is currently no subscriber using eDirectory connector, therefore the code of eDirectory connector was removed from the LDAP connector bundle.
  • Support for BEA/Oracle WebLogic deployment was removed. Weblogic support was maintained because of a special arrangements with one of the first midPoint subscribers. Weblogic support is not needed by that subscriber and it is not used by any other subscriber. Therefore support for Weblogic deployment is no longer available. Tomcat is not the only supported web container. Support for any other containers is not planned.

Releases Of Other Components

...

  • Functionality that is marked as EXPERIMENTAL is not supported for general use (yet). Such features are not covered by midPoint support. They are supported only for those subscribers that funded the development of this feature by the means of platform subscription or for those that explicitly negotiated such support in their support contracts.
  • MidPoint comes with bundled LDAP Connector. Support for LDAP connector is included in standard midPoint support service, but there are limitations. This "bundled" support only includes operations of LDAP connector that 100% compliant with LDAP standards. Any non-standard functionality is explicitly excluded from the bundled support. We strongly recommend to explicitly negotiate support for a specific LDAP server in your midPoint support contract. Otherwise only standard LDAP functionality is covered by the support. See LDAP Connector page for more details.
  • MidPoint comes with bundled Active Directory Connector (LDAP). Support for AD connector is included in standard midPoint support service, but there are limitations. Only some versions of Active Directory deployments are supported. Basic AD operations are supported, but advanced operations may not be supported at all. The connector does not claim to be feature-complete. See Active Directory Connector (LDAP) page for more details.
  • MidPoint comes with bundled Active Directory Connector (LDAP), which includes support for PowerShell scripting. This scripting is supposed to be used to supplement creation of Active Directory (windows) accounts by using simple scripts. It is not supposed to be used to manage Microsoft Exchange accounts. Management of Exchange accounts can be quite a complex matter, requiring complicated PowerShell scripts. Support for the use of this connector to manage Exchange accounts has to be purchased separately.
  • The PowerShell capability of  Active Directory Connector (LDAP) will be migrated to a dedicated connector in midPoint 4.1 or later. Once this capability is migrated, PowerShell scripting will no longer be supported as part of bundled midPoint connectors. There will be special connector for that purpose and support for such connector will be sold separately. Therefore, if you need support for PowerShell scripting, we recommend explicitly negotiating such support in your midPoint support contract. MidPoint subscribers that purchased their full subscription before the release date of midPoint 4.0 should not be affected by this change. However we recommend to check status of your subscription coverage by contacting Evolveum.
  • MidPoint 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.
  • There is an option to modify midPoint to support LDAP and CAS authentication by using Spring Security modules. This method is used in several midPoint deployments. However, such authentication modules are not officially supported as part of usual midPoint subscriptions. Only community-level support is provided for those modules. Commercial-grade support for this authentication method is available, but it has to be explicitly negotiated in a subscription contract.
  • MidPoint user interface has flexible (fluid) design and it is able to adapt to various screen sizes, including screen sizes used by some mobile devices. However, midPoint administration interface is also quite complex and it would be very difficult to correctly support all midPoint functionality on very small screens. Therefore midPoint often works well on larger mobile devices (tablets) it is very likely to be problematic on small screens (mobile phones). Even though midPoint may work well on mobile devices, the support for small screens is not included in standard midPoint subscription. Partial support for small screens (e.g. only for self-service purposes) may be provided, but it has to be explicitly negotiated in a subscription contract.
  • There are several add-ons and extensions for midPoint that are not explicitly distributed with midPoint. This includes midPoint plug-in for Eclipse IDE, extension of Jasper studio, Java client library, various samples, scripts, connectors and other non-bundled items. Support for these non-bundled items is limited. Generally speaking those non-bundled items are supported only for platform subscribers and those that explicitly negotiated the support in their contract. For other cases there is only community support available. For those that are interested in official support for IDE add-ons there is a possibility to use subscription to help us develop midPoint studio (
    Jira
    serverEvolveum Jira
    serverId701b45f2-090c-3276-8ac9-f45eedf731bc
    keyMID-4701
    ).
  • The integration of Jaspersoft Studio for midPoint (a.k.a. "Jasper plugin") will not work with midPoint 4.0. The reporting web service was changed and the plugin was not yet adapted to that change. This work is planned for later. The priorities will be determined by platform subscribers.
  • MidPoint contains a basic case management user interface. This part of midPoint user interface is not finished. The only supported part of this user interface is the part that is used to process requests and approvals. Other parts of case management user interface are considered to be experimental, especially the parts dealing with manual provisioning cases.

...