Include and Exclude Characters from Password policies are not Inherited tor Entries

Hello,
Thank you for your post.

We are already investigating this behavior. At the moment, it seems to be related to the “Inherited” state, as it works correctly when the value is set manually.
We understand this may be inconvenient, and we appreciate your patience while we look into it.
We will update you as soon as we have new information to share.
Thanks
Stephan

i can confirm that the problem is only related to Inherited State.

Actually, I do not need the feature to define password policies on individual entries.
I only need the global password policy to work correctly.

Hey,
thank you for the update.

Yes, even though Inherited is set as the default, you can change the setting to System settings to ensure the global password policy is applied correctly.

Until we are able to provide a fix, you can adjust this setting on all required entries by using Batch Edit in combination with the Advanced Search feature:
https://docs.devolutions.net/rdm/commands/view/search/advanced/
https://docs.devolutions.net/rdm/commands/edit/batch-edit/

For new entries, you can also set the default policy by using a template:
https://docs.devolutions.net/rdm/commands/file/templates/

This workaround should help in the meantime. If you have any questions or need assistance with these steps, please don’t hesitate to let us know — we’ll be happy to help.

Thanks,
Stephan

Hello,

We've found and fixed the inherited issue. You can expect this to take effect with the upcoming 2025.3.30 version (or the upcoming 2026 version, whichever comes first).

Regards,