Policies

Definition

A Policy is a set of rules or actions that apply to a scope of managed objects. These rules or actions can be executed periodically or when an object (which belongs to the scope) is treated.

Rules can be configured on Policies. Depending on the type of assigned Policy, the rules may be omitted if they don't make sense, meaning the assignment is direct (from an Object Type to a specific Policy).

Types of Policies

Business Policies — A Business Policy allows to configure how to trigger actions on Object Types through a Feature with an optional configured Workflow.

Object Policies — An Object Policy is an Identity Management Service Policy allowing to execute arbitrary actions on Managed Objects, either on a scheduled basis, or in reaction to an Object Operation.

Deduplication Policies — A Deduplication Policy describes how duplicates should be searched for when creating a managed object.

Feature Access Policies — A Feature Access Policy is composed of a right which encompasses several Features.

Manual Provisioning Policies — A Manual Provisioning Policy allows to define that manual provisioning or deprovisioning Workflow is launched when the Role assignment status changes.

Object Lifecycle Policies — An Object Lifecycle Policy allows to configure rules, on all Object Types, that will alter an Object attribute directly when certain lifecycle events occur.

Password Policies — A Password Policy determines how passwords should be composed and which rules apply to their lifecycle.

Role Request Policies — A Role Request Policy allows to define if a Role can be requested, for whom, by whom, and using which Workflow.

Workflow Administration Policies — A Workflow Administration Policy is composed of a right which encompasses several Features.

Memority MFA Account Policies — A Memority MFA Policy allows to configure how multi factor authentication should be applied to a population of user

Configuration

Each type of policy have the following global properties

Domain

Code

Version and encoding : Each FAP starts by announcing the version and encoding.

XML

<?xml version="1.0" encoding="UTF-8"?>
<kit:DataSet xmlns:ctd="http://www.memority.com/citadel/1_0" xmlns:ctdbpmn="http://www.memority.com/citadel/bpmn/1_0" xmlns:ctdbum="http://www.memority.com/citadel/bum/1_0" xmlns:ctdcore="http://www.memority.com/citadel/core/1_0" xmlns:ctdidm="http://www.memority.com/citadel/idm/1_0" xmlns:ctdrep="http://www.memority.com/citadel/rep/1_0" xmlns:ctdrule="http://www.memority.com/citadel/rule/1_0" xmlns:ctdtnt="http://www.memority.com/citadel/tnt/1_0" xmlns:kit="http://www.memority.com/toolkit/1_0" xmlns:rule="http://www.memority.com/toolkit/rule/1_0" xmlns:ruleaddon="http://www.memority.com/toolkit/addons/rule/1_0" xmlns:search="http://www.memority.com/toolkit/search-expression/1_0" xmlns:settings="http://www.memority.com/toolkit/addons/settings/1_0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <ctdbum:PolicyType id="requestPolicy_1">
   </ctdbum:PolicyType>
</kit:DataSet>

DataSet : Each FAP starts by announcing the DataSet.

The policy configuration