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:

• We have quite a precise plan for the next release.
• We have a feature development plan for following few releases (see below).
• We have rough plan for next few years and we have a vision where to take the project in a decade or so.

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.

Roadmap Overview

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

Latest Release: 3.7 (Darwin)

MidPoint is currently high-quality product developed for more than 6 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:

• Identity Management
  
  • Account provisioning (create, read, update, delete accounts)
  • Support for mapping and expressions to determine account attributes
  • Processing and computation fully based on relative changes
  • Provisioning robustness and consistency
  • Integration of Identity Connector Framework (ConnId)
  • Web-based administration GUI
  • Flexible identity repository implementations and SQL repository implementation
  • Live synchronization
  • Reconciliation
  • Advanced Hybrid RBAC support and flexible account assignments
  • Password policies
  • Password recovery
  • Flexible reporting
  • Notifications
  • Workflow support (based on Activiti)
  • Generic Synchronization
  • Entitlements
  • Self-registration
• Identity Governance
  • Governance-enabled Advanced Hybrid RBAC
  • Organizational Structure management
  • Access Certification
  • Segregation of Duties
  • Deputy
  • Personas
  • Multi-level approvals with escalation
• Platform
  • Groovy, JavaScript and Python Customization expressions
  • PolyString support allows automatic conversion of strings in national alphabets
  • Multi-node task manager component with HA support
  • Custom schema extensibility
  • Auditing to files or database table
  • Data representation in XML, JSON a YAML
  • Web service, Java and REST APIs
  • Lightweight deployment structure

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.

Next Release: 3.8

This plan is also reflected in our task tracking system (jira).

Planned release date: spring 2018

The major features planned for the next release include:

• Performance improvements
• User interface improvements
• Manual connector improvements
• GDPR features (experimental)
  

Fluid Features and Subscriptions

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.

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:

• Developer SDK
• Connector Framework Evolution
• Fully customizable forms
• Flexible data caching
• Advanced SoD support and reporting

• History and Rollback

• Advanced Role Administration

• Account archivation

• Manual Processing

... and Beyond

We have a long-term vision that guides the project.

Influencing Roadmap

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, "buying" a feature 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.

There is also one free way how to influence midPoint development: voting for issues. There is a voting options in our Jira. Registered users can vote for issues, which gives us a hint where to focus during planning and development.

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.

Loading …

T	Key	Summary
	MID-4529	Better credentials UI
	MID-3261	Separate end-user GUI
	MID-3259	Pass-through authentication
	MID-2905	SoD exlusive role assignment in the context of some object
	MID-2698	Scripted summary header
	MID-2647	Smart data export (machine readable reports)
	MID-2575	End user role management
	MID-2567	Form definition
	MID-2483	Advanced Segregation of Duties
	MID-2364	Report by e-mail
	MID-2355	Reload connectors and extension schema automatically
	MID-2256	Credentials: SSH keys
	MID-2215	Role exclusivity based on expressions
	MID-2214	Hierarchical selection widget
	MID-2050	LDAP connector OpenLDAP livesync using OpenLDAP replication protocol
	MID-1934	Add tenant concept to authorizations
	MID-1905	Expose validation methods using a webservice/REST
	MID-1820	Validity recompute in roles (immediate assignment)
	MID-1769	Make midPoint self-aware regarding version, display in Server Tasks-Nodes for multi-node deployment
	MID-1685	Allow (user recomputation) tasks to reference object templates

Showing 20 out of 34 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="4059cc60-d9e5-44af-b8aa-476be8b94045"><ac:parameter ac:name="columns">type,key,summary</ac:parameter><ac:parameter ac:name="url">https://jira.evolveum.com/sr/jira.issueviews:searchrequest-xml/10900/SearchRequest-10900.xml?tempMax=1000</ac:parameter><ac:parameter ac:name=": = | RAW | = :">columns=type,key,summary|url=https://jira.evolveum.com/sr/jira.issueviews:searchrequest-xml/10900/SearchRequest-10900.xml?tempMax=1000</ac:parameter><ac:parameter ac:name=": = | TOKEN_TYPE | = :">BLOCK</ac:parameter></ac:structured-macro>

See Also

• Vision
• Development Process
• Jira Roadmap

External links

• What is midPoint Open Source Identity & Access Management
• Evolveum - Team of IAM professionals who developed midPoint