1 vote
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
Use Case
We manage multiple service accounts and application credentials where the password format follows a predefined structure, for example:
AppName!MMYY
Example password:
Hi cyrillschreiber,
Thank you for sharing this request.
Our password generator is designed around security best practices, and this isn't something we're looking to implement in the short term.
We do understand that real-world environments can come with constraints, and we appreciate you taking the time to describe your use case.
Best regards,
Simon Leroux
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
Hello,
I'm curious, if it's just an append at the end to the generated password (this could be an option in the password template), would that be enough? I'm not sure how easy it would be to include the date in an existing pattern.
Regards
David Hervieux