立即与支持人员聊天
与支持团队交流

Password Manager 5.9.7 - Administration Guide (AD LDS Edition)

About Password Manager Getting Started Upgrading Password Manager Password Manager Architecture
Password Manager Components and Third-Party Solutions Typical Deployment Scenarios Password Manager in Perimeter Network Management Policy Overview Password Policy Overview reCAPTCHA Overview User Enrollment Process Overview Questions and Answers Policy Overview Data Replication Phone-Based Authentication Service Overview Configuring Management Policy
Management Policies
Checklist: Configuring Password Manager Understanding Management Policies Configuring Access to the Administration Site Configuring Access to the Self-Service Site Configuring Access to the Helpdesk Site Configuring Questions and Answers Policy Workflow overview Custom workflows Custom Activities Self-Service Workflows Helpdesk Workflows User Enforcement Rules
General Settings
General Settings Overview Search and Logon Options Import/Export Configuration Settings Outgoing Mail Servers Diagnostic Logging Scheduled Tasks Web Interface Customization Instance Reinitialization Realm Instances AD LDS Instance Connections Extensibility Features RADIUS Two-Factor Authentication Unregistering users from Password Manager Working with Redistributable Secret Management account Email Templates
Password Policies One Identity Starling Reporting Appendix A: Accounts Used in Password Manager for AD LDS Appendix B: Open Communication Ports for Password Manager for AD LDS Appendix C: Customization Options Overview Glossary

Creating a Password Policy

To create a password policy, you need add a connection to the AD LDS instance to which this policy will be applied.

The account you use to access the AD LDS instance for which you want to create password policies should have the following permissions:

  • The Read permission for attributes of the groupPolicyContainer objects.
  • The Write permission to create and delete the groupPolicyContainer objects in the System Policies container.
  • The permission to create and delete container and the serviceConnectionPoint objects in Group Policy containers.
  • The Read permission for the attributes of the container and serviceConnectionPoint objects in Group Policy containers.
  • The Write permission for the serviceBindingInformation and displayName attributes of the serviceConnectionPoint objects in Group Policy containers.

To connect to AD LDS instance

  1. On the home page of the Administration site, click the Password Policies tab.
  2. Click Connect to AD LDS instance to add an instance for which you want to create password policies.
  3. If connections already exist, select a connection from the list. If you want to create a new connection, click Add new connection.
  4. If you selected to create the new connection, in the Connect to AD LDS Instance dialog, configure the following options:
    • In the Server name on which AD LDS instance is installed text box, type the name of the server to which you want to connect.
    • In the Port number (LDAP or SSL) text box, enter the port number that you specified when installing the AD LDS instance. If you select the Use SSL check box, enter the SSL port number; otherwise, LDAP port number. It is recommended to use SSL in your production environment.
    • In the Application directory partition text box, enter the name of the application directory partition from the AD LDS instance to which you want to connect.
    • In the Application directory partition alias text box, type the alias for the application directory partition which will be used to address the partition on the Self-Service site.
    • In the Access account section, select Password Manager Service account to have Password Manager access the AD LDS instance using the Password Manager Service account, otherwise, select The following Active Directory account or The following AD LDS account radio button and enter the required user name and password.
  5. Click Save.

For more information on modifying settings for the connection, see AD LDS Instance Connections.

To create a password policy

  1. On the home page of the Administration site, click the Password Policies tab.
  2. Click the <N> One Identity Password Policies or One Identity Password Policies are not configured link under the application directory partition that you want to manage.
  3. On the One Identity Password Policies for <application directory partition> page, click the Add a policy button or Add new password policy link.
  4. In the Add New Policy dialog box, type a name for the new policy and click Save.

To configure settings for a password policy

  1. On the home page of the Administration site, click the Password Policies tab.
  2. Click the <N> 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. On the Policy Settings tab of the Password Policy Properties dialog box, view or modify the following options, and then click Save:
Table 17: Password Policy Properties

Option

Description

Disable this policy

Select this check box to temporarily turn off the policy.

Policy name

View or modify the name of the password policy.

  1. Click the Policy Rules tab to configure the password policy rules by using the procedure outlined in Configuring Password Policy Rules, and then click Save.
  2. Click the Policy Scope tab to manage the password policy links by using the procedure outlined in Managing Password Policy Scope, and then click Save.

Managing Password Policy Scope

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

Applying Password Policies

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.

IMPORTANT:

  • While configuring the Policy Scope in Password Policy Properties window, it is mandatory to add both the group and the Organizational unit that the user is part of, for the policy rules to get applied for the users accessed in the self-service site.
  • It is not possible to configure the same domain multiple times in a user scope, whereas multiple domains can be configured to the userscope.

The table below provides more information on different scenarios.

Let us consider the following groups/OU

NOTE: Do not define both OU and the group in the Management policy scope for the set password policy rule to get applied in the self-service site.

 

S.No Userscope

 

 

Password Policy Scope

 

 Password Policy Logged in self-service site

Is Password Policy applicable?

 

Included Group Included OU

Excluded Group

Excluded OU

OU Group
1. Group1 OU1

 

 

 OU1 Group1 Password Policy1 User1

Yes

2. Group1 OU2

Group2

 

 OU1 Group2

 

Password Policy2

 

 User2

No

3.

Group3

OU1

Group1

 

OU2

Group3

User2

No

4.

Group3

OU3

 

OU1

OU3

Group3

 

Password Policy3

 

User3

Yes

5.

Group2

OU2

 

 

OU1

Group2

User2

No

6.

Group1

OU1

 

OU4

OU4

Group1

 

Password Policy4

 

User1

No

7.

Group2

OU2

 

OU5

OU5

Group2

User2

No

8.

Group3

OU3

Group1

 

 

Group3

 

Password
Policy 5

 

User3

No

9.

Group3

OU3

Group2

 

OU3

 

User3

No

 

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.

Changing Policy Priority

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.

 NOTE: Only priority of policies with the same scope can be changed.

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.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级