cyrillschreiber

Hi David,

thanks for your question.

An append at the end wouldn’t be enough for us. We need to update only the date part inside a fixed password pattern.

Example:

AppName!MMYY

Only MMYY should change automatically (e.g. monthly), while the rest stays the same.

This could be done with date variables in password templates or a partial rotation rule.

I understand the security concerns, but for our environment this would be a useful optional feature.

Best regards,

Cyrill

Thank you for your response.

I understand the security considerations behind this decision. However, due to constraints in our environment, this functionality would be very helpful for us.

I would appreciate it if you could consider this for a future implementation or as an optional feature. This would not serve as a general guideline, but rather as an optional capability for specific use cases.

I would also appreciate it if you could keep me informed whether this will be implemented or not.

Kind regards,

Cyrill Schreiber

Currently, passwords stored in Devolutions can be updated manually or fully rotated. In our environment, we have a specific requirement where only the date portion of a password (month and year) should be automatically updated, while the rest of the password remains unchanged.

Requested Functionality

• Ability to automatically update only the month and year within a password.

• The remaining part of the password should stay static.

• The update should be configurable (e.g., monthly or yearly).

• Ideally, this could be implemented via:

  • Password templates with date variables (MM/YYYY or similar), or

  • A built-in rule for partial password rotation.

Use Case

We manage multiple service accounts and application credentials where the password format follows a predefined structure, for example:

AppName!MMYY

Example password:

• Current password: FinanceApp!0626

• Next automatic update: FinanceApp!0726