Password Manager 5.11.1 - Administration Guide (AD LDS Edition)

This section provides information on how to apply a password policy to organizational units and groups in a managed AD LDS instance.

In Password Manager (PM) application, scopes can be defined at multiple levels. Scopes act as a boundary in which you can define the groups and Organization Unit (OU), and can also associate policies into it.

The Default Management Policy allows you to configure both the user scope and the help desk scope. In the Management Policy scope, an admin can also associate the workflows, activities, and Q&A policy to the configured user groups and OU.

While configuring the user scope/help desk scope, an admin must define either a Group or an OU to indicate which group or OU can access the self-service site/helpdesk site. This means the users who are part of the configured group/OU comes under included group category. You could also define a different group/OU under an excluded group category. This means users who are part of these excluded group or OU cannot access self-service site/helpdesk site.

In case of Password Policy scope, admin needs to ensure the following

• Password policies should only be applied to the user groups/ OUs that are part of the Userscope.
• Group that will be associated into the password policy scope must be part of the OU as well. This means users who are part of the group must also be the part of the OU as those users will have the same set of activities to be performed in the self-service site.
• An Administrator can create one or more password policies and can map each policy to single/ multiple user groups or OUs.
• By default, the newly created password policy is linked to the Domain name created in the management policy scope and gets applied to the “Authenticated users group. It means that all the users that are part of the usergroups and OUs configured in the user scope, will have the password policy applied.
• Group that will be associated into the password policy scope must be part of the OU as well. This means users who are part of the group must also be the part of the OU as those users will have the same set of activities to be performed in the self-service site.

The table below provides more information on different scenarios.

Let us consider the following groups/OU

To link a password policy to organizational units and groups

1. On the home page of the Administration site, click the Password Policies tab.
2. Click the One Identity Password Policies link under the application directory partition that you want to manage.
3. On the One Identity Password Policies for <application directory partition> page, click Edit under the policy whose properties you want to view or modify.
4. Click the Policy Scope tab.
5. Click the Add button under This policy is applied to the following organizational units, and then browse for an organizational unit.
6. Click the Add button under This policy is applied to the following groups, and then browse for a group.
7. Click Save.

When multiple password policies affect an organizational unit or a group, only the policy with the highest priority is applied to such group or organizational unit. A newly created password policy is disabled by default.

To change policy priority

1. On the home page of the Administration site, click the Password Policies tab.
2. Click the One Identity Password Policies link under the AD LDS instance for which you want to change the policy link order and click Policy priority.
3. In the Change Policy Priority dialog box, move policies up or down in the list by selecting them and clicking the Move Up or Move Down buttons.

Password Manager uses a set of powerful and flexible rules to define requirements for passwords. Each password policy has rules that are configured independently of the rules in other policies.

For each password policy, you can set up the following rules:

• Password age rule. Ensures that users cannot use expired passwords or change their passwords too frequently.
• Length rule. Ensures that passwords contain the required number of characters.
• Complexity rule. Ensures that passwords meet minimum complexity requirements.
• Required characters rule. Ensures that passwords contain certain character categories.
• Disallowed characters rule. Rejects passwords that contain certain character categories.
• Sequence rule. Rejects passwords that contain more repeated characters than it is allowed.
• User properties rule. Rejects passwords that contain part of a user account property value.
• Symmetry rule. Ensures that password or its part does not read the same in both directions.
• Custom rule. Use this rule to enter the settings of the local or domain password policy applied to the server on which AD LDS is running, if you want to display these settings to users on the Self-Service site when users reset or change passwords. You can also use this rule to display your custom messages and to hide the configured policy rules.