When User Principal Name (UPN) is used as service account, installing a Password Manager hotfix can lock the service account.

Workaround

To solve the problem:

1. Change the service account to the domainname\username format.

2. Provide a password for the same service account user.

3. Install the Password Manager hotfix.

Following a Password Manager upgrade, the General > Settings > Scheduled Tasks > Active Directory Sites task is disabled.

Workaround

After upgrading Password Manager to a newer version, enable the Active Directory Sites task manually.

When scheduled from the secondary instance of the Password Manager server, the General Settings > Unregister Users task does not run.

Workaround

Schedule the Unregister Users task on the primary instance of Password Manager.

If the application pool identity is a domain user with minimal permissions, then Web interface customization changes are not applied to the Self-Service and Helpdesk Sites.

In the General Settings > Instance Reinitalization page, the Corporate phone attribute is not imported from the primary instance to the secondary instance.

Workaround

Update the Corporate phone attribute manually on the secondary instance to have the same value as on the primary Password Manager instance.

If the Password Manager Self-Service Site contains an IPv6 address, the location-sensitive authentication (LSA) feature does not work.

Workaround

LSA currently supports IPv4 addresses only. Therefore, do not access the Password Manager Self-Service Site from an external network where the request contains an IPV6 address.

When configuring a dictionary rule in the Password Manager Administration Site, the Policy Rules > Dictionary Rule > Enable dictionary lookup to reject passwords that contain > Beginning characters of a dictionary word setting does not work correctly if you specify only 2 beginning characters.

Workaround

One Identity recommends using the A complete word from the dictionary (QPMDictionary.txt) setting when configuring a dictionary rule.

If no appropriate authentication methods are configured for it, the Forgot My Password screen may appear blank in the Password Manager Self-Service Site or Helpdesk Site.

Workaround

In the Password Manager Administration Site, One Identity recommends configuring the Register workflow with Security Questions as one of its registration modes.

When a symmetry rule is configured with the Policy Rules > Symmetry Rule setting of the Password Manager Administration Site, it may fail to validate passwords containing non-consecutive characters.

Workaround

Do not use the Policy Rules > Symmetry Rule > Maximum number of consecutive characters within a password, that read the same in both directions (pass4554word) setting.

In a Password Manager for AD LDS environment, if the User Scope is configured with an AD LDS account, the Forgot My Password and Manage My Passwords workflows will fail.

Workaround

When configuring a User Scope, do not use The following AD LDS account setting of the Access account > Edit AD LDS Instance Connection dialog.

When a Questions and Answers Policy is updated with any language other than English, users may receive both the default and the custom email notifications on the Password Manager Self-Service Site.

Workaround

For the Email user if workflow succeeds workflow, change the value of the Select email template to use setting to Customize.

When searching users with reCAPTCHA enabled, not entering reCAPTCHA for the second time results in a non-human readable error message.

Workaround

Always search for users with the correct username and with the reCAPTCHA check completed.

Upgrading Password Manager from version 5.6.3 to 5.9.x keeps the previous My Questions and Answers profile workflow.

Workaround

To solve the problem:

1. In the Password Manager Administration Site, navigate to the My Questions and Answers profile workflow.

2. Open Workflow Settings > Availability.

3. Set Enable the workflow to Never.

4. Select Show the workflow on the Self-Service site.

5. To apply your changes, click OK.

The User Status Statistics scheduled task may fail intermittently.

After upgrading to Password Manager 5.9.x, the My Notifications custom workflow cannot be edited in the Password Manager Self-Service Site.

Workaround

One Identity recommends to use the legacy Self-Service Site to edit the My Notifications workflow.

When using Password Manager for AD LDS, the Password Policies page of the Administration Site is not updated when a password policy is created.

Workaround

After a new Password Policy is created, click Save, and immediately cancel the Add New Policy wizard. The page will refresh and list the new policy.

After upgrading to Password Manager for AD LDS 5.9.x, the General Settings > Search and Logon Options menu may display an error when its settings are modified.

Workaround

To solve this problem:

1. In the Password Manager for AD LDS Helpdesk Site, navigate to General Settings > Search and Logon Options.

2. In the Users must enter the following user account attribute for identification setting, change the value from sAMAccountName to cn.

Domain users may not be able to access the Password Manager Administration Site, even if they are members of the local PMAdmin group.

Workaround

When using Password Manager 5.8.x or newer, domain users can access the Administration Site only if they are members of both the local PMAdmin group, and either the IIS_IUSRS group or the Administrators group.

In Password Manager for AD LDS, certain column data required for custom activities are not available in generated reports.

After upgrading Password Manager from an earlier version to 5.9.x, the upgrade process may create duplicate URL references for the Password Manager User Site.

Workaround

Manually delete URL shortcuts that are not required.

When a Password Manager for AD LDS instance and the Password Manager for AD LDS server instance are not configured on the same machine, Password Policy Rules are not displayed in the new and legacy Password Manager for AD LDS Self-Service Sites.

Workaround

Configure the Password Manager for AD LDS instance and the Password Manager for AD LDS server instance on the same machine.

The user search settings of the Password Manager for AD LDS Helpdesk Site may work incorrectly.

Workaround

To solve the problem:

1. In the Password Manager for AD LDS Helpdesk Site, navigate to General Settings > Search and Logon Options.

2. Use the cn attribute instead of mail to search for users.

When editing a Questions and Answers Policy, you may be unable to edit or delete translated questions.

Workaround

To edit existing translated questions, add another translated language.

The Password Manager Self-Service Site may not launch on Secure Password Extension (SPE) through a 32-bit operating system.

Workaround

If you have a 32-bit operating system, One Identity recommends to use the legacy Self-Service Site.

When a password is changed from the target Active Directory (AD) system to that of the source AD, One Identity Quick Connect may be unable to synchronize passwords.

Workaround

Restart the Quick Connect Capture Agent Service on all the source and target systems.

In Password Manager versions 5.8.2 and 5.9.x, you can only reconnect to a domain on the second attempt.

Workaround

To solve the problem:

1. In the Password Manager Administration Site, select the User Scope, Helpdesk Scope or Password Policy you want to configure.

2. Click Add domain connection twice to add a new domain connection.

In email notifications, the #OPERATOR_ACCOUNT_NAME#, #OPERATOR_IP#, #WORKFLOW_RESULT#, and #WORKFLOW_SUMMARY# parameters are not populated.

On Windows Server 2019, the Password Manager Service and One Identity rSMS Service may stop.

Workaround

To solve the problem, make sure that the domain controller machine and the clients are at two separate entities.

When editing a dictionary file between the size of 10–20 MB from a Password Policy, the web browser session may crash, and an error may appear in the Windows Event Viewer.

Workaround

If you must modify a dictionary file larger than 10 MB, edit it from the domain machine where Password Policy Manager (PPM) is installed.