Fixed various security issues.

Previously, when using phone authentication with Starling 2FA, authentication did not work with phone numbers longer than 12 digits.

This issue is now fixed, and phone authentication now accepts phone numbers longer than 12.

Previously, when configuring a custom management account under General Settings > Domain connections for a domain, and the custom management account was not a user of that domain, then having another user with the same name (but a different password) on that domain resulted in the authentication of that user failing every time when a scheduled task tried binding onto the configured domain. Following these failed authentication attempts, the user could be locked out.

This issue is now fixed so that the authentication process now uses the correct domain information, provided in the Add New Domain Connection > User name field.

Previously, toast notifications for the Secure Password Extension (SPE) component did not work properly if the management policy only had the Organizational Units (OUs) of the users configured, but not their groups. This issue is now fixed.

Previously, creating a custom password policy, and specifying a custom rule for it in Password Policies > <domain-password-policy> > Edit > Policy Rules > Custom Rule resulted in the following issues if the custom rule have contained any line breaks:

• In the Password Manager User Site, the specified text was converted to a single line.

• In the Password Manager Self-Service Site, only the contents of the first line appeared.

Both of these issues are now fixed, and line breaks are handled properly on both sites.

Previously, deleting a custom workflow resulted in the Password Manager Administration Site being stuck in a loading state, forcing users to reload the page.

This issue is now fixed.

Previously, when creating a new workflow with the workflow designer, drag-and-dropping activities into it or moving activities within it could result in the workflow designer showing incorrect configuration dialogs, or showing drag-and-dropped items in an incorrect order.

This issue is now fixed, so drag-and-dropping and reordering activities in custom workflows work properly.

Fixed a login issue affecting the Password Manager Administration Site.

Previously, when configuring a password reset workflow based on embedded connectors, the workflow did not work for LDAP target systems, even if the rSMS LDAP Connector has been configured in the Reset password in connected systems through embedded connectors activity, as described in Knowledge Base Article 332671.

This issue is now fixed, and users can reset the password of their account in the remote LDAP database if the embedded rSMS LDAP Connector is configured in the workflow.

Previously, the redirection behavior of the Save and Cancel buttons in the available General Settings options was inconsistent, with some of them redirecting users to the home page of the Password Manager Administration Site, while others keeping users at the currently opened setting page when clicking them.

This issue has been fixed with the following changes:

• Clicking Save buttons no longer redirects users to the home page.

• All Cancel buttons have been removed from every General Settings option page.

Previously, when using two Management Policies with the same user groups included in their User Scopes, and having a Helpdesk group assigned to the Helpdesk Scope of the second Management Policy, attempting to select a found user on the Helpdesk Site could result in a system error.

This issue is now fixed, and Helpdesk users now can select found users without getting any errors.

Previously, setting the General Settings > Search and Logon Options > Do not allow users to search for their accounts > Users must enter the following user account attribute for identification (this may slow down the performance) attribute to sAMAccountName resulted in a Value cannot be null critical error when attempting to search and select users that belong to a different management policy.

This issue is now fixed, and the Password Manager Helpdesk Site returns a No accounts matching your search criteria have been found message in such cases.

Previously, attempting to log in to the Password Manager Self-Service Site with an expired password resulted in an Incorrect password error message, even if the password policies of the organization allowed users to authenticate with expired passwords.

After their second attempt, users could log in to the Self-Service Site with their expired password: however, any workflow that used the Authenticate with password activity still failed on the first try when the users used their correct but expired password.

This issue is now fixed, and the Self-Service Site accepts the expired user password on the first attempt.

Previously, routing to the Password Manager Self-Service Site did not work properly if the site URL have contained query parameters (for example, when routing to the site via the Offline Password Reset component).

This issue was caused by the routing not being case insensitive in such cases, and has been fixed in Password Manager 5.9.7.