Chat now with support
Chat with Support

Password Manager 5.9.7 - Administration Guide

About Password Manager Getting Started Password Manager Architecture
Password Manager Components and Third-Party Solutions Typical Deployment Scenarios Password Manager in Perimeter Network Management Policy Overview Password Policy Overview Secure Password Extension Overview reCAPTCHA Overview User Enrollment Process Overview Questions and Answers Policy Overview Password Change and Reset Process Overview Data Replication Phone-Based Authentication Service Overview
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 Notification Activities 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 Domain Connections Extensibility Features RADIUS Two-Factor Authentication Unregistering users from Password Manager Working with Redistributable Secret Management account Email Templates
Upgrading Password Manager Administrative Templates Secure Password Extension Password Policies One Identity Starling Reporting Password Manager Integration Appendixes Glossary

Active Directory Sites

By specifying Active Directory sites in the domain connection settings you select the site in which you want Password Manager to replicate changes as soon as they occur in other sites. This can reduce downtime that users may experience when your environment has several Active Directory sites and changes may not get immediately replicated between the sites.

For example, when users unlock their accounts on the Self-Service site, this operation may occur in one site. But when they attempt to log in to their computers, this operation may occur in another site, to which the information about the unlocked account has not been replicated yet. In this case, users will not be able to log in until the information is replicated to the second site. To mitigate this issue, select the Active Directory sites in which you want to replicate changes immediately in the domain connection settings.

Note, that you cannot force replication of changes related to password policies. Such changes are replicated by Active Directory.

To specify Active Directory sites

  1. On the Administration site, click the General Settings|Domain Connections tab.
  2. On the Domain Connections page, select the domain connection for which you want to specify domain controllers and click Edit.
  3. On the Advanced Settings tab of the Edit Domain Connection dialog, click Add under the Active Directory sites table, select required sites, and click Add.
  4. Click Save. Note, that the updated settings will be applied everywhere where this domain connection is used.

Changes Propagation

After you specify the Active Directory sites in which you want to push changes, you can also select what kind of changes to propagate. The following options are available:

  • Propagate changes related to the user’s account in Active Directory
  • Propagate changes related to the user’s Questions and Answers profile
  • Propagate password-related changes

Propagating account-related changes

Select this option to propagate information about unlocking and enabling user accounts in Active Directory. It is recommended to use this option when a managed domain has users in multiple Active Directory sites.

Propagating Q&A profile-related changes

Select this option to propagate information about editing, locking and unlocking Questions and Answers profile, and passcodes issued by Helpdesk. It is recommended to use this option when users and Password Manager Service use domain controllers from different sites. In this case, if users update their Q&A profiles using Secure Password Extension (via the domain controller in one site), and then attempt to use the profiles on the Self-Service (via the domain controller in another site), they may encounter the issue when the updated Q&A profile is not yet available because of intersite replication latency.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating