Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

MidPoint 3.7 and later


There are many ways how to assign roles, orgs and services. Many roles are assigned using a manual or partially-manual process. But there is almost always some degree of automation when at least some roles are assigned to users according to fixed rules. This page describes the mechanism to automatically assign roles in midPoint.

Autoassignment Conditions in Roles

Perhaps the most convenient way to automatically assign a role is to use autoassignment condition in a role:

Autoassignment mapping in a role
                        <code>employeeType == 'intern'</code>

The role above will be automatically assigned to any user that has property employeeType set to intern. As all midPoint mapping even this mapping is relativistic. If user becomes an intern (the employeeType property is changed) then the role is automatically assigned. When the user stops being an intern the role is unassigned.

See Role Autoassign Configuration page for more details.

Autoassignment in Object Template

Autoassignment in roles is simple and elegant, but it has several disadvantages. However, even complex role autoassignment cases can be handled by using object template. The roles can be automatically assigned by using object template mappings:

Autoassignment in object template
    <name>User Template</name>

The mapping above will create assignment for any role which name matches with a value of organization user property. Therefore a single mapping can be used to assign a wide range of roles.

See Object Template page for more details about object template mechanism. The Expression page describes the details of assignmentTargetSearch expression evaluator that is frequently used for this purpose.

Roles Within Roles

TODO: inducement

TODO: exclusion and pruning

See Also

  • No labels