The long-term plan for midPoint GUI is to use existing administration GUI for both administration and end-user interactions. We are working on a fine-grained authorization subsystem that will allow limiting users to a specific parts of the midPoint functionality. This is also planned to work with a delegated administration and workflows. The current plan is to have basic framework in place in version 2.2 and to have a complete subsystem in 3.0 or 3.1 (all the plans still subject to change).
What are the experimental features?
Some features of midPoint are in progress. Such features are marked as "experimental" in the schema and may be changed or removed.
There are two places in
System Configuration where you can turn the experimental features on (by default they are turned off).
Enable Experimental Code
Can be used to turn on any experimental backend code.
<systemConfiguration> . . . <internals> <enableExperimentalCode>true</enableExperimentalCode> . . . </internals> </systemConfiguration>
Enable Experimental Features
Can be used to turn on any experimental GUI-based features. As this is part of adminGuiConfiguration, it may be in the
System configuration object or in roles/organizations assigned to the users.
<systemConfiguration> . . . <adminGuiConfiguration> . . . <enableExperimentalFeatures>true</enableExperimentalFeatures> </adminGuiConfiguration> </systemConfiguration>
I need midPoint to support feature X. What should I do?