With Beta 2024.1.7.0 the Ribbon Buttons for Copy Password or Username to Clipboard aren't working anymore. In the dialog "View Password" the Copy Buttons are working as expected. Copy Host, Domain and Name seem also working in the ribbon. Can you reproduce the behavior?
Thanks and best regards
Hello,
Thank you for reporting this issue.
We were unable to reproduce this behavior internally.
What data source type are you connected to?
On what entry type do you get this behavior?
Best regards,
Érica Poirier
The Datasource is MSSQL. This happens with all kinds of entries like Username/Password, Host, SSH, as well as all kinds of linked Entries. The Popup appears that the credentials were copied, but the clipboard is empty afterwards.
It seems that the clipboard content is deleted, as previously existing clipboard content is no longer available.
Best regards
I think this could be related to the legacy clipboard copy method. We have activated the "Legacy" method as this is the only working setting in our remote administration environments.
If I change the setting to "Paste Once (secure)" the copy buttons in the "View Password" window start acting like the ribbon buttons - it stops working. If I toggle the setting back to "Legacy" the "View Password" works again, but the ribbon stays the same. Is it possible that the ribbon copy function ignores the "Legacy" setting?
Best regards
Hello,
Thank you for your feedback.
Even with the Legacy option set, we cannot reproduce your issue.
Could you please try the latest RDM beta 2024.1.11 we just released?
Do you have administrator rights on the entries? If not, what permissions do you have on those entries?
Could you please try to troubleshoot using the Clipboard Diagnostic tool?
https://docs.devolutions.net/kb/remote-desktop-manager/troubleshooting-articles/clipboard-diagnostic/
Let us know if you find any relevant information.
Best regards,
Érica Poirier
I updated to the latest beta but the problem remains the same. I have admin rights on the entries. The troubleshooting tool hints that my assumption was right. Using the Copy Username an Copy Password buttons on a host entry leads to this output:
Clipboard - Copy Clipboard - Paste Once - Count : 1 Clipboard - Empty Clipboard - Promise - Format : 49676 Clipboard - Promise - Format : 49484 Clipboard - Promise - Format : 49483 Clipboard - Promise - Format : 49677 Clipboard - Promise - Format : 13 Clipboard - Render - Requester : 3476544 - Format : 13 Clipboard - Render - Allow listed - Rrequester : 3476544 Clipboard - Requester : 3476544 - Process Id : 23920 - Name : PicaShell Clipboard - Set - Format : 13 Clipboard - Done! Clipboard - Empty Clipboard - Clear
Using the Copy Password Button in the "View Password" window leads to this output:
Clipboard - CopyMethod : Legacy Clipboard - SetText Clipboard - Clear
So the ribbon buttons ignore the Legacy setting while the "View Password" window works correctly in our environment. The Copy once method won't work as the Clipboard Sharing (PicaShell) grabs the clipboard content by design.
Best regards
Small addition: Adding a PicaShell Disallow Rule works and brings back the functionality. But the inconsistent behavior remains as the root cause of the problem.
Best regards
Hello,
Thank you for your feedback.
I guess you still get the same behavior with the latest 2024.1.12 version.
You mentioned PicaShell. Are you using RDM in a Citrix environment? If so, we do not own such an environment, so it's not easy for us to reproduce this behavior you are experiencing.
As you found that PicaShell interferes, even with the disallow rule, a workaround would be to set the Credential copy options to 2 buttons.
Best regards,
Érica Poirier
I just tested the latest 2024.1.17 release and the the problem is resolved. The Legacy switch seems working again for the ribbon copy actions.
Thank you for fixing this issue!
Nonetheless, it was a good opportunity to rethink the clipboard sharing options and if we switch to the more secure option with the appropriate additional rules to make it work in our environment.
Best regards
Hello,
Thank you for your feedback. That's good news that the latest build has solved your issue.
Best regards,
Érica Poirier