MidPoint 3.0 "Newton"

Release 3.0 is a tenth midPoint release code-named Newton. The 3.0 release brings new major features such as entitlements, delegated administration, generic synchronization and RESTful interface.

This release starts a new era of midPoint development. The Newton release is introducing features that are quite unique in the identity management field. It goes beyond traditional identity management. This midPoint version joins together provisioning-based identity management (IDM), privileged identity management (PIM) and organizational structure management into a single, unified model. The features can be combined into a powerful configurations that are still simple and easy to maintain. As usual we are following our development principles and we are reusing existing mechanisms, generalizing them and making the much more powerful.

Newton goes beyond traditional identity management. It is much more than just synchronization of accounts and users. The support for entitlements allows to extend the capabilities to groups, teams, privileges, resource-side roles and similar concepts which is moving midPoint in the direction of privileged identity management (PIM). MidPoint now allows seamless synchronization of these objects, therefore groups can be easily synchronized with midpoint roles which in turn can be synchronized with groups on other resources or even complex technical roles defined on the resource side. MidPoint goes beyond the tradition even in this aspect. As midPoint really understands the entitlements it can do very smart tricks. E.g. if a role is a representation of a group on resource and a user is assigned to that role user’s account can be automatically assigned to this group. All of that with just a handful of configuration statements. This is all considerably generic therefore similar principle can be applied to synchronization of organizational structure as well. And (as expected) all the midPoint principles can be applied to these new features. Therefore RBAC roles can be applied to simplify synchronization of organizational unit. Or even the roles itself. Which naturally creates the very powerful concept of meta-roles. And all of that is achieved mostly by reusing existing midPoint features. This is what we had in mind during last few midPoint releases. We have been slowly (you wound say "evolutionarily") introducing small changes to the code, one bit in each release. Now it all culminates with midPoint 3.0. We strongly believe that "Newton" is a very suitable name for this release.

MidPoint version 3.0 is named after one of the greatest English scientists. By doing so we would like to thank our English partner Salford Software for their contribution to the midPoint project.