Password Generator - Copy to clipboard - copy with newline as a separator

Hello,

Thank you for the request, I think it makes sense to change the behavior to be separated by new lines rather than commas. I've opened a ticket.

Regards,

Hello,

We've made the change internally and the password generator's "copy to clipboard" button will now separate the passwords with a new line rather than a comma, when your RDM is configured to use the "legacy" paste mode (which you were already using if you encountered the "comma" separation).
This change will be available starting with 2025.2.26.0.

Regards,

Yes, it works great, thank you!

I hope you'll also solve other problems with passwords, like the:

• Password generator - accessed from the entry - does not remember recently selected template/mode,
• The Generate menu item always generates mediocre passwords, no matter what you select in Password generator.

Thank you for the feedback, I'm happy to hear it works well for you.

As for your other points, from what I understand this is linked to your thread here: https://forum.devolutions.net/topics/50650/generate-option-in-entry-properties-produces-weak-passwords

We are planning on making two changes:

• We're changing the default value for the password template on entries to be inherited by default. This means that by simply setting the template at the root-level, every entry you create will refer to this template, and the "generate" button is based on that template whenever one is configured.
• We will add support for "shared password templates" in SQLite. This is the reason why the dropdown is currently empty for this feature in SQLite. We don't support (and don't want to support) local password templates to be configured in entries. This would require you to recreate your current (local) templates to be shared ones.

I think with these two changes the experience you're looking for will be quite enhanced. We'll also see about having a way to remember the last used password template, we just have to make sure it doesn't conflict with our other features.

Regards,

Thank you for elaborate response.

> We're changing the default value for the password template on entries to be inherited by default. This means that by simply setting the template at the root-level, every entry you create will refer to this template, and the "generate" button is based on that template whenever one is configured.

That is a very comprehensive solution. But I think this may be hard to discover/comprehend for users. My mental model was much simpler - whatever profile is currently selected in the Password generator window, it should also apply to the "Generate" menu item.

But if you'll make it sufficiently easy to discover, it will be super powerful. Such as - as a consultant - for company "A" set their preferred password generation policies, for company "B" set what they prefer etc.

> We don't support (and don't want to support) local password templates to be configured in entries.

Of course!

Thanks a lot. RDM is gaining more powers and flexibility with each release 💪 Thanks for listening to users, I really appreciate that!

Discoverability of features is always a difficult challenge and it's not always one type of solution that will help in all scenarios.

But if you'll make it sufficiently easy to discover, it will be super powerful. Such as - as a consultant - for company "A" set their preferred password generation policies, for company "B" set what they prefer etc.

That's exactly the goal of why we're switching the mode to be inherited by default, to help administrators more easily configure this type of environment.

We hope to keep improving our products and striking a good balance between a discoverable and powerful featureset. User feedback has been at the core of Devolutions since its inception, so we're always happy to hear that our users appreciate our efforts!

As a note, I'll also be making a post in your other thread regarding these requests, as that's the one linked to the currently opened tickets, it'll be easier for us to track that way.

Regards,