This release is planned. Therefore the information presented here is incomplete and inaccurate.
For information regarding the latest stable release please see Release 3.7.1
Release 3.8 is a twenty fifth midPoint release code-named Watt. The 3.8 release brings TODO.
Planned release date: May 2018
Majority of the work on the Watt release was done by the Evolveum team. However, this release would not be possible without the help of our partners, customers, contributors, friends and families. We would like to express our thanks to all the people that contributed to the midPoint project both by providing financial support, their own time or those that maintain a pleasant and creative environment for midPoint team. However, midPoint project would not exist without proper funding. Therefore we would like to express our deepest gratitude to all midPoint subscribers that made midPoint project possible.
midPoint 3.8 provides following features:
- Common identity management data model
- Extensible object types:
- Numerous built-in properties
- Extensibility by custom properties
- Completely schema-aware system
- Dynamic schema automatically retrieved from resource
- Support for primitive data types
- Native support of multi-value attributes
- Limited support for complex data types
- Processing and computation fully based on relative changes
- Off-the-shelf support for user password credentials
- Off-the-shelf support for activation (users, roles, orgs, services)
- Enabled/disabled states (extensible in the future)
- Support for user validity time constraints (valid from, valid to)
- Object template to define policies, default values, etc.
- Ability to use conditional mappings (e.g. to create RB-RBAC setup)
- Ability to include other object templates
- Global and resource-specific template setup
- Representation of all configuration and data objects in XML, JSON and YAML
- Extensible object types:
- Identity management
- Enabling and disabling accounts
- Support for mapping and expressions to determine account attributes
- Multi-layer attribute access limitations
- Provisioning dependencies
- Higher-order dependencies (enables partial support for circular provisioning dependencies)
- Provisioning robustness - ability to provision to non-accessible (offline) resources
- Provisioning consistency - ability to handle provisioning errors and compensate for inconsistencies
- Support for tolerant attributes
- Ability to select tolerant and non-tolerant values using a pattern (regexp)
- Support for volatile attributes (attributes changed by the resource)
- Matching Rules
- Matching rules to support case insensitive attributes, DN and UUID attributes, XML attributes, etc. (extensible)
- Automatic matching rule discovery
- Ability to execute scripts before/after provisioning operations
- Advanced support for account activation (enabled/disabled states)
- Standardized account activation that matches user activation schema for easy integration
- Ability to simulate activation capability if the connector does not provide it
- Support for account lock-out
- Support for account validity time constrains (valid from, valid to)
- Support easy activation existence mappings (e.g. easy configuration of "disables instead of delete" feature)
- Support for mapping time constraints in activation mappings that allow configuring time-related provisioning features such as deferred account delete or pre-provisioning.
- Ability to specify set of protected accounts that will not be affected by IDM system
- Support for base context searches for connectors that support object hierarchies (such as LDAP)
- Bulk actions
- Passive Attribute Caching (EXPERIMENTAL)
- Partial multi-tenancy support
- Live synchronization
- Ability to execute scripts before/after reconciliation
- Correlation and confirmation expressions
- Conditional correlation expressions
- Concept of channel that can be used to adjust synchronization behaviour in some situations
- Generic Synchronization allows synchronization of roles to groups to organizational units to ... anything
- Self-healing consistency mechanism
- Advanced RBAC
- Expressions in the roles
- Hierarchical roles
- Conditional roles and assignments/inducements
- Parametric roles (including ability to assign the same role several times with different parameters)
- Temporal constraints (validity dates: valid from, valid to)
- Role catalog
- Role request based on shopping cart paradigm
- Several assignment enforcement modes
- Ability to specify global or resource-specific enforcement mode
- Ability to "legalize" assignment that violates the enforcement mode
- Rule-based RBAC (RB-RBAC) ability by using conditional mappings in user template and role autoassignment
- Entitlements and entitlement associations
- GUI support for entitlement listing, membership and editing
- Entitlement approval
- Identity governance
- Powerful organizational structure management
- Workflow support (based on Activiti engine)
- Declarative policy-based multi-level approval process
- Visualization of approval process
- Object lifecycle property
- Object history (time machine)
- Policy Rules as a unified mechanism to define identity management, governance and compliance policies
- Segregation of Duties (SoD)
- Many options to define role exclusions
- SoD approvals
- SoD certification
- Assignment constraints for roles and organizational structure
- Access certification
- Ad-hoc recertificaiton
- Basic role lifecycle management (role approvals)
- Deputy (ad-hoc privilege delegation)
- Escalation in approval and certification processes
- Rich assignment meta-data
- Expressions, mappings and other dynamic features
- Sequences for reliable allocation of unique identifiers
- Customization expressions
- PolyString support allows automatic conversion of strings in national alphabets
- Mechanism to iteratively determine unique usernames and other identifier
- Function libraries
- User profile page
- Password management page
- Role selection and request dialog
- Email-based password reset
- Flexible identity repository implementations and SQL repository implementation
- Fine-grained authorization model
- Organizational structure and RBAC integration
- Delegated administration
- Password management
- Password distribution
- Password policies
- Password retention policy
- Self-service password management
- Password storage options (encryption, hashing)
- Mail-based initialization of passwords for new accounts
- CSRF protection
- Scheduled reports
- Lightweight reporting (CSV export) built into user interface
- Comprehensive reporting based on Jasper Reports
- Post report script
- Administration documentation publicly available in the wiki
- Architectural documentation publicly available in the wiki
- Schema documentation automatically generated from the definition (schemadoc)
Changes with respect to version 3.7
- User interface improvements
- Data model improvements
- Full implementation of
- TODO: locality, etc.
- Full implementation of
- Security improvements
- Password Policy: prohibited projection values
- Negative item enumeration in authorizations (
- Provisioning Propagation
- Ad-hoc provisioning script execution
- Performance and scalability improvements
- Miscellaneous improvements
- Improved handling of function library updates
- Minor mapping improvements
- Improved SMS gateway support (HTTP POST method)
- CSV connector supports script execution
- Active Directory connector supports CredSSP version 5 and 6 (see CVE-2018-0886)
Oracle database 11g is no longer supported. It is replaced by Oracle 12c database support.
PostresSQL 8.4.x is no longer supported.
MySQL 5.6 family is no longer supported.
Microsoft SQL 2008 and 2008 R2 are no longer supported.
Old CSVFile Connector is deprecated and it is no longer bundled with midPoint.
Parsing of search filters was made a bit more strict: certain classes of errors related to
exists filter clauses are now checked during filter parsing instead of previous approach that checked them when the filter was to be applied. This means that roles or other objects containing such malformed filters are only partially usable: they can be read from the repository (to be used during midPoint execution, displayed via standard GUI or on Repository objects page); however, such objects cannot be modified in any way. The only way how to modify them is to fix malformed filters first using Repository objects page.
Release 3.8 (Watt) is intended for full production use in enterprise environments. All features are stable and well tested - except the features that are explicitly marked as experimental or partially implemented. Those features are supported only with special subscription and/or professional services contract.
- MidPoint 3.8 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.
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 with 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 contact Evolveum for more details).
- OpenJDK 8 (1.8.0_91, 1.8.0_111, 1.8.0_151)
- Sun/Oracle Java SE Runtime Environment 8 (1.8.0_45, 1.8.0_65, 1.8.0_74, 1.8.0_131)
- Apache Tomcat 8 (8.0.14, 8.0.20, 8.0.28, 8.0.30, 8.0.33, 8.5.4)
- BEA/Oracle WebLogic (12c) - special subscription required
Web container (application server) support
Currently there are no plans to remove support for deployed midPoint installation using a WAR file. However, it is possible that this deployment form will get phased out eventually unless there are active subscribers preferring this deployment method. MidPoint subscription is strongly recommended if you plan to use this method in the future.
- H2 (embedded, only recommended for demo deployments)
- PostgreSQL 9 (9.1, 9.2, 9.3, 9.4, 9.4.5, 9.5, 9.5.1)
- MariaDB (10.0.28)
- MySQL 5.7 (5.7)
Supported MySQL version is 5.6.10 and above (with MySQL JDBC ConnectorJ 5.1.23 and above).
MySQL in previous versions didn't support dates/timestamps with more accurate than second fraction precision.
- Oracle 12c
- Microsoft SQL Server 2012, 2014
- Firefox (any recent version)
- Safari (any recent version)
- Chrome (any recent version)
- Opera (any recent version)
- Microsoft Internet Explorer (version 9 or later)
Recent version of browser as mentioned above means any stable stock version of the browser released in the last two years. We formally support only stock, non-customized versions of the browsers without any extensions or other add-ons. According to the experience most extensions should work fine with midPoint. However, it is not possible to test midPoint with all of them and support all of them. Therefore, if you chose to use extensions or customize the browser in any non-standard way you are doing that on your own risk. We reserve the right not to support customized web browsers.
Microsoft Internet Explorer compatibility mode is not supported.
Important Bundled Components
|ConnId||188.8.131.52||ConnId Connector Framework|
|LDAP connector bundle||1.6||LDAP, Active Directory and eDirectory connector|
|CSV connector||2.2||Connector for CSV files|
|DatabaseTable connector||184.108.40.206||Connector for simple database tables|
Download and Install
Stand-alone deployment model
MidPoint 3.7 deployment method has changed. Stand-alone deployment is now the default deployment method. MidPoint default configuration, scripts and almost everything else was adapted for this method.
- New midPoint users and new deployments should simply follow the installation manual.
- Existing deployments may keep using exactly the same configuration as before. Deployment of midPoint as Web Application is still supported as an alternative. However, stand-alone deployment is now the primary option. It is recommended to migrate the deployment based on application server to a stand-alone deployment in the future. See our brief migration guide.
|Installing midPoint v3.7|
MidPoint is software that is designed for easy upgradeability. We do our best to maintain strong backward compatibility of midPoint data model, configuration and system behavior. However, midPoint is also very flexible and comprehensive software system with a very rich data model. It is not humanly possible to test all the potential upgrade paths and scenarios. Also some changes in midPoint behavior are inevitable to maintain midPoint development pace. Therefore we can assure reliable midPoint upgrades only for midPoint subscribers. This section provides overall overview of the changes and upgrade procedures. Although we try to our best it is not possible to foresee all possible uses of midPoint. Therefore the information provided in this section are for information purposes only without any guarantees of completeness. In case of any doubts about upgrade or behavior changes please use services associated with midPoint subscription or purchase professional services.
Upgrade from midPoint 3.0, 3.1, 3.1.1, 3.2, 3.3, 3.3.1, 3.4, 3.4.1, 3.5, 3.5.1, 3.6 and 3.6.1
Upgrade path from MidPoint 3.0 goes through midPoint 3.1, 3.1.1, 3.2, 3.3, 3.4.1, 3.5.1 and 3.6.1. Upgrade to midPoint 3.1 first. Then upgrade from midPoint 3.1 to 3.1.1, from 3.1.1 to 3.2 then to 3.3, then to 3.4.1, 3.5.1, 3.6.1, 3.7.1 and finally to 3.8.
Upgrade from midPoint 3.7 and 3.7.1
MidPoint 3.8 data model is essentially backwards compatible with previous midPoint versions. However, there were changes that may affect some deployments:
- Object subtype was fully implemented. Subtype is now the recommended way how to sort object such as users into smaller categories and types. Subtype is a direct replacement for
serviceType. Introduction of subtype as step towards schema unification. Existing deprecated properties (
serviceType) still work in the same way as they have worked in previous midPoint versions (with one exception, see below). However,
subTypeproperty should be used as a replacement whenever possible. The only difference in functionality is that personas construction will now set
subTypeproperty in new personas instead of
employeeTypeproperty as it was in previous midPoint versions.
- TODO: locality, costCenter, etc.
Even though the basic database model is compatible with the previous versions, the underlying database schema was significantly modified due to performance and scalability improvements. Therefore the usual database-only upgrade procedure is not applicable for upgrades to midPoint 3.8.
TODO: export/import procedure
MidPoint 3.8 is a release that fixes some issues of previous versions and there were also improvements to existing funtionality. Therefore there are some changes that may not be strictly backward compatible with previous versions:
- Version numbers of some bundled connectors have changed. Therefore connector references from the resource definitions that are using the bundled connectors need to be updated.
Changes in initial objects since 3.7 and 3.7.1
MidPoint has a built-in set of "initial objects" that it will automatically create in the database if they are not present. This includes vital objects for the system to be configured (e.g. role
superuser and user
administrator). These objects may change in some midPoint releases. But to be conservative and to avoid configuration overwrite midPoint does not overwrite existing objects when they are already in the database. This may result in upgrade problems if the existing object contains configuration that is no longer supported in a new version. Therefore the following list contains a summary of changes to the initial objects in this midPoint release. The complete new set of initial objects is in the
config/initial-objects directory in both the source and binary distributions. Although any problems caused by the change in initial objects is unlikely to occur, the implementors are advised to review the following list and assess the impact on case-by-case basis:
- TODO: system config: logging appender!!!
Bundled connector changes since 3.7 and 3.7.1
- The LDAP connector and AD Connector were upgraded to the latest available version. The reason is a vulnerability in CredSSP protocol version 4 and earlier (CVE-2018-0886). Microsoft implemented CredSSP versions 5 and 6 to mitigate the issue. However those versions are incompatible with previous versions, therefore new implementation has to be done in the connector.
- CSV connector now supports script execution (executing operating system commands).
Behavior changes since 3.7 and 3.7.1
- URLs used by Stand-Alone Deployment were changed to match the URLs used by Tomcat-based deployments of midPoint 3.6 and earlier. This means that all deployment forms now use
/midpoint/context root path in the URL by default (e.g.
http://localhost:8080/midpoint/). This choice was made based on user feedback to keep the compatibility with previous midPoint versions and to keep the two deployment models as closely aligned as possible. For the stand-alone deployment there is an automatic HTTP redirect from the root URL (e.g.
http://localhost:8080/) to midPoint context root (e.g.
http://localhost:8080/midpoint/). Therefore in midPoint 3.7.1 both deployment method should behave in a natural, expected and compatible way.
- Processing of authorizations for proxy authentication in the REST interface was corrected. The processing of proxy authorizations now behave as documented.
- Processing of object authorizations was corrected. Authorizations now take into consideration also the properties of existing removed containers even in replace and id-only delete cases. Therefore, appropriate property authorization is needed even when deleting a value that contains those properties.
- Password reset schema was deprecated. Existing password reset configuration still works, but it will be replace by new password reset configuration in the future.
Public interface changes since 3.7 and 3.7.1
- REST interface was extended with experimental password reset method.
- TODO: audit table?
Important internal changes since 3.7 and 3.7.1
These changes should not influence people that use midPoint "as is". These changes should also not influence the XML/JSON/YAML-based customizations or scripting expressions that rely just on the provided library classes. These changes will influence midPoint forks and deployments that are heavily customized using the Java components.
- Definition of Unified Connector Framework (UCF) interface was changed in order to improve support for manual connectors. As this is experimental interface, please see source code history for description of changes.
- Definition of Java manual connector interface (abstract classes) was changed. As this is experimental interface, please see source code history for description of changes.
Known Issues and Limitations
There is a support to set up storage of credentials in either encrypted or hashed form. There is also unsupported and undocumented option to turn off credential storage. This option partially works, but there may be side effects and interactions. This option is not fully supported yet. Do not use it or use it only at your own risk. It is not included in any midPoint support agreement.
Native attribute with the name of 'id' cannot be currently used in midPoint ( MID-3872 - Attribute 'id' Open ). If the attribute name in the resource cannot be changed then the workaround is to force the use of legacy schema. In that case midPoint will use the legacy ConnId attribute names (icfs:name and icfs:uid).
JavaDoc is temporarily not available due to the issue in Java platform. This issue is fixed in Java 9 platform, but backport of this fix to Java 8 is (quite surprisingly) not planned.
As all real-world software midPoint 3.7 has some known issues. Full list of the issues is maintained in jira. As far as we know at the time of the release there was no known critical or security issue.
There is currently no plan to fix the known issues of midPoint 3.7 en masse. These issues will be fixed in future maintenance versions of midPoint only if the fix is requested by midPoint subscriber. No other issues will be fixed - except for severe security issues that may be found in the future.
The known issues of midPoint 3.7 may or may not be fixed in midPoint 3.8. This depends on the available time, issue severity and many variables that are currently difficult to predict. The only reliable way how to make sure that an issue is fixed is to purchase midPoint subscription. Or you can fix the bug yourself. MidPoint is always open to contributions.
This may seem a little bit harsh at a first sight. But there are very good reasons for this policy. And in fact it is no worse than what you get with most commercial software. We are just saying that with plain language instead of scrambling it into a legal mumbo-jumbo.