Password Policy: Filter for correct policy on password field click and confusing error message - Devolutions Password Manager

1 vote

gernoth

Published 23 days ago

We are using different Password vaults for different Tiering levels.

Source is dvls: We have set a password policy for every vault:

When adding a new credential entry in devolutions password manager, it does not show the correct policy set for the vault:
(yes, i know that clicking on the three dots - Generate from policy and selecting policy works, but when policy is shown on click into field it should be the correct one)

Thats extremly confusing for users, because they click on create a new password and get an error afterwards because the password does not match the password policy.

The error is even more confusing:

The user should get feedback why an error occured (for example password does not meet password policy), not just an error occured.(like when using a pwned password)

Thank you!

79d49d8b-46c7-4500-bc26-b46150c16485.png

e82a7504-a4cd-493b-8d02-eb79c367c8c6.png

f45d414b-12a8-4b15-b34f-fb33a043a938.png

All Comments (2)

Dany Galarneau

Published 23 days ago

Hi,

Thanks for reporting this and for the detailed explanation.

I can confirm that this is indeed a bug. The password generator should respect the password policy configured for the current vault when creating a new credential entry.
I also agree that the current error message is too generic. When a password does not meet the configured policy, the user should receive a clear explanation of what caused the validation to fail.
I'll create a ticket so we can address both the incorrect policy being shown/used and improve the error feedback.

We’ll keep you updated and let you know as soon as we have more information or a fix available.

Best regards,

Dany Galarneau

Published 22 days ago

Hello,

We have released a new version, 2026.2.3, which includes modifications to the password policy. These changes should resolve the issue you were experiencing.
Please update to the latest version and let us know if the issue persists.

Best regards,

Dany Galarneau