MidPoint does not have a roadmap in a traditional sense. MidPoint development process is considerably agile and the development priorities of midPoint project are dynamic. The roadmap is mostly influenced by midPoint subscribers and contributors. MidPoint project is planned in a rolling wave:
As the project rolls out the plan is also made more precise. The plan is reviewed before each new release starts which is at least twice a year.
|4.0 LTS "Gutenberg"|
|Fall 2018||Spring 2019||Winter 2019-2020||Fall 2020||Spring 2021|
Service account management (partial)
User experience improvements
Impact analysis, reorganizations
Limits and thresholds (experimental)
Asynchronous (messaging) connector options
Flexible authentication (part 2)
Docker containerization improvements
Limits and thresholds (multi-node)
Connector framework improvements
Status reporting and notification improvements (experimental)
Flexible authentication (part 1)
|Active Directory connector improvements |
|Support for multiple equivalent accounts on a resource (inbound)|
|Asynchronous (messaging) connector options (prototype)|
|LDAP and AD connector improvements|
|Minor user experience improvements |
|Data model and interface cleanup||User experience improvements (server tasks)|
|User interface testing framework||Long-term support stabilization|
|Java 11 support|
SPONSORED: feature that was funded by midPoint customer/partner or a free slot available for sponsored feature (see below)
SUBSCRIPTION: feature that was funded by midPoint platform subscription (see below)
CONTRIBUTED: significant portion of this feature was developed by a third party and contributed to midPoint project
LTS: Long-term support release. See Long-Term Support.
Even though we are trying really hard to make this plan as precise as possible, it is still just a plan. It can change at any moment. It is not recommended to depend on any features in this roadmap. The roadmap is driven by the priorities given to us by platform subscribers. There are also other things that can influence the roadmap, such as unexpected maintenance work, surge in support effort, security issues and so on. The roadmap is dynamic, and even the plan for currently-developer release may change as late as few weeks before release.
Even if a feature is already marked as SUBSCRIPTION, it does not mean that it will be developed precisely as planned. The plan can still change. Subscriber that is sponsoring this feature may re-prioritize. The scope may change to adapt to subscriber's changed requirements. Or we may negotiate planning changes with that subscriber and the feature may be re-planned. The only reliable way how to make sure that you can depend on this plan is to secure a platform subscription and set your own priorities and dates for the features that you depend on.
MidPoint is currently high-quality product developed for more than 7 years. MidPoint has a solid architectural foundation that was proven in practice. The current set of features provides good fit for almost any environment: enterprise (both employee and customer identities), telco, cloud, Internet, etc.
Current features include:
More detailed information about current project state can be found on midPoint Releases page and especially in the release notes of the most recent release.
This plan is also reflected in our task tracking system (jira).
Planned release date: spring 2019
The major features planned for the next release include:
The plan is for Gutenberg to be the first Long-Term Support release.
Each midPoint release has a reserved capacity for subscriber features.
MidPoint is an open source product that is developed by professional developers. This approach brings unique combination of software freedom and quality. However professional development needs to be continually funded. This funding comes from midPoint subscriptions. MidPoint subscribers may use their subscription to vote for a specific feature to be placed on roadmap. We refer to the feature that is placed on the roadmap by any of these methods as subscriber feature. Each midPoint release has a reserved capacity for the features that directly or indirectly contribute to the funding of midPoint development. If the funding of next release cannot be secured by the means of subscriptions, some midPoint developers must provide the funding using alternative methods (mostly professional services). These alternative methods leave only a very small portion of the developer's time that can be dedicated to midPoint development. As a consequence, subscriber feature slots cannot be filled in by community feature requests otherwise midPoint development funding would be at risk. If sufficient funding for midPoint development is not secured by subscriber features the midPoint roadmap has to be reduced and the development capacity reserved to the subscriber feature slots is lost. Therefore if you depend on a specific roadmap feature please consider purchasing midPoint platform subscription and use that to make sure that the feature is placed on the roadmap.
The privilege to influence midPoint roadmap is included only in some of midPoint subscription programs. Platform subscription offering is designed especially for this purpose.
Except for subscriber features the Evolveum company invests into one or two major features or architectural improvements in each release. This investment is to make sure that the quality of the midPoint architecture increases and that midPoint will continually gain new progressive features. This helps midPoint to maintain its status of state-of-the-art identity management system.
There are also some features that are not yet assigned to specific releases:
In addition to that there are other planned features:
History and Rollback
Advanced Role Administration
There was a possibility to pay for a development of a specific midPoint feature in the past. That possibility is currently being phased out. There may still be a possibility for a very limited sponsoring, but that possibility will be discontinued in 2018. MidPoint platform subscription is a recommended method for sourcing midPoint features.
Motivation: Ad-hoc sponsoring provides funding for a development of a new feature. But such sponsoring cannot provide funding for maintenance of the feature. Only subscription can do that. Long-term stability and development is paramount for us. Therefore we have decided to decline sponsoring offerings in favour of subscriptions.
If you are interested in sponsoring new midPoint features, please consider purchasing platform subscription.
We have a long-term vision that guides the project.
The roadmap is governed mostly by the people that support midPoint project, either financially or by contributing work. Therefore if you need to influence priorities of midPoint development, please consider a donation, purchase of a subscription or lending a helping hand. Please contact us if you are interested in helping financially. If you want help by investing your time and brains, please see the Participation page.
Following table contains all features that are not planned yet and are labeled as product-feature.
If you would like to have some of the features in next releases then you can vote for them. If this table is missing some of your favorite features then you can create Jiras and vote for them.
Tip: Don't forget to label your features as product-feature to highlight them for others.