UCS 2.4 - Univention

4.5.11.1 Adding a policy
4.5 Univention Directory Manager modules
Univention Directory Manager allows direct as well as indirect creation of policies. When directly creating
a policy, the user can use the LDAP Browser to jump to the desired location within the LDAP directory and
select the desired type of policy via the select list Add new object at current position.
Alternatively, new policies can be directly created via the policies wizard (Policies ➞ Add). After having
selected the desired type of policy and the target container, the new values of the policy can be entered.
Policies can also be indirectly created via Univention Directory Manager by filling in or editing a tab for an
object if the caption of the tab is set in square brackets, and Select configuration is available (see chapter
4.5.11.4). The values adapted on these tabs are stored as policies.
By default, policies are stored in the container policies which was automatically generated during the
creation of the domain. For further structuring, the container policies includes containers for each policy
type.
When adding or editing objects, policies of a suitable type are available from the registered policies con-
tainers in the select list Select configuration on the relevant tab.
Attention:
It has to be ensured that the container wherein a policy is created, is registered as a standard container
for policies (see chapter 4.5.12.7). Otherwise, the policy will not be found. The automatically generated
container policies is already registered as a standard container for policies.
Settings, which can be made for the different types of policies, will be explained together with the tabs
of the corresponding objects. When directly adding a policy, the entry field Name is displayed, wherein
a random name for the policy can be entered. Furthermore, an Object tab will only be displayed when
directly creating or editing a policy.
’Object’ tab
This tab is available for every policies object. It enables the user to make settings relating to object
classes and attributes.
Required object classes
Object classes can be stated here, to which the objects have to belong so that they can be linked to
this policy.
Prohibited object classes
Object classes can be stated here, to which the objects to be linked with this policy may no belong.
Fixed attributes
Attributes can be selected here, the values of which may not be changed by subordinate policies.
Empty attributes
Attributes can be selected here, which are to be set to empty in the policy, meaning they will be
stored without containing a value. This can be useful for removing values inherited by an object
109