The complete list* of subscription features that can be used in a production environment:
- Clustering
- MidPoint GUI message removal
- Email notification footer message removal
- Report footer message removal
- Support for a generic repository database
(2) MidPoint displays information about a missing subscription on the login screen, the registration screen, and the identity recovery screen, as well as in the GUI footer. If there is no active subscription in place, it will show “No active subscription. Please support midPoint by purchasing a subscription.”. If a subscription is active, no information about the subscription is displayed in the aforementioned places. During a subscription renewal phase, which is right after a subscription expires, there might be a grace period when the message “Your subscription has expired. You have X days to renew it.” will be shown instead of information about having no active subscription.
(3) MidPoint uses a mechanism to notify users about relevant changes in midPoint and/or connected resources. For example, a user (or a user’s supervisor, or the person who requested the operation, the security manager, etc.) may be notified when one of the user’s accounts is created, modified, or removed; or when the midPoint user record is created, when the password is changed, or when there is a new work item to process. If there is no active subscription, a recipient will see a message that says “No active subscription. Please support midPoint by purchasing a subscription.” in the footer of an email. If there is an active subscription in place, there is no default message set in the footer.
(4) The same footer is also used in the reports generated by midPoint.
(5) MidPoint has to store its own data in a database, which we call the repository. MidPoint stores all data there: users, roles, shadow objects representing accounts, configuration, etc., and needs an SQL database engine to do that. Since the version 4.4, midPoint can use features specific to PostgreSQL to its advantage (using a native PostgreSQL repository implementation), hence it is in users’ and Evolveum’s best interest to migrate to the PostgreSQL database. Support for all generic SQL database engines was deprecated years ago and replaced by a superior functionality offered by PostgreSQL. However, Evolveum is still being asked to continue supporting the old ways, which we are open to do for paying customers. If a generic SQL repository is used without an active subscription, the GUI gets disabled and the only option is to activate a subscription.
MidPoint displays information about the origin of midpoint.jar on the About page to inform users whether or not Evolveum guarantees the integrity of the deployed midPoint version. If the official build is used, it will display “Official build by Evolveum”. If a custom build is used with possible modifications of the source code, it will display “Unofficial build”. There is also a possibility to just extend the official build with a code overlay. In that case the page will display the text “Overlay”.
MidPoint was, is, and will always remain an open source project, and no parts of the code are removed or kept secret. Evolveum is committed to keeping everything publicly available. Our decision to make some midPoint features only available to subscribers is not meant to limit anyone. It is meant to motivate midPoint users to be fair and keep open source development sustainable for the benefit of us all.
*Please note, Evolveum reserves the right to modify this list at its sole discretion, either by adding new subscription features or discontinuing existing ones. Changes to the subscription features will be communicated in writing to customers and partners at least two (2) months prior to the effective date of such changes, either via the website or by sending a separate email.