UCS 2.4 - Univention

4.5 Univention Directory Manager modules
Illustration 4.11 which shows the Policies tab for the domain, i.e. the root of the LDAP directory of a
typical UCS installation.
Inheritance cannot be switched off directly. Yet, the object can be linked to a new policy in which the
fields can be freely defined, meaning they can also be defined as being empty.
To link the object to another/new policy, the appropriate policy type has to be clicked on the Policies
tab. Another tab will then open where the settings for the policy can be made. Alternatively, an
existing policy can be selected from the Select configuration list (see chapter 4.5.11.4).
After confirmation by clicking [OK], the new settings are adopted, unless the editing process as a
whole is aborted. A new or changed policy is stored under a unique name which is derived from
the name of the container (see chapter 4.5.11.4). The original settings are retained unchanged if
[Cancel] is clicked.
To unlink a policy from its present object, the checkbox behind the policy is to be ticked first. If the
user then clicks [Disconnect], Inherited will be displayed on the tab instead of the previous policy.
The unlinking process is confirmed by clicking [OK].
4.5.11.4 Linking policies to other objects
Square brackets on a tab indicate that the settings on this tab can be performed via policies.
The Select configuration list shows existing policies which can be applied to the present position. The
preset configuration is Inherited in which the configuration parameters of the superordinate container are
adopted for the current object.
Once a configuration has been selected, the values resulting from the policy will be displayed in the
corresponding fields on the tab. Greyed-out values cannot be changed. All values displayed in black
lettering as well as all empty fields can be adjusted at random.
A new policy is generated by Univention Directory Manager from the new values. A container for each
policy type is prepared in the policies container. The policies generated by Univention Directory Manager
are automatically stored in these containers.
A policy generated by Univention Directory Manager is named after the object for which it was created. If
there is already a policy of the same name, the suffix _uv0 will be appended to the name of the new policy.
Further policies with conflicting names will be numbered consecutively, by the endings _uv1, _uv2, etc..
The policy can be found under this name in the container for the corresponding policy type. If one of the
existing policies is changed, these changes will affect all objects to which the policy in question is applied.
If, in contrast, a value is changed via the Policies tab of the object for which the policy was created, a new
policy will automatically be created with the changed values, and the original policy remains unchanged.
So, the new values apply only to the present object and, if applicable, to subordinate objects.
111