Users

All Posts (36)

avatar

John Doe 25

2024.1.7.0 Beta Copy to Clipboard not working in Ribbon

avatar
avatar
avatar

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

2024.1.7.0 Beta Copy to Clipboard not working in Ribbon

avatar
avatar
avatar

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

2024.1.7.0 Beta Copy to Clipboard not working in Ribbon

avatar
avatar
avatar

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

2024.1.7.0 Beta Copy to Clipboard not working in Ribbon

avatar
avatar
avatar

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

2024.1.7.0 Beta Copy to Clipboard not working in Ribbon

avatar
avatar
avatar

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

2024.1.7.0 Beta Copy to Clipboard not working in Ribbon

avatar
avatar
avatar

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

2023.1.10 seems breaking "Move to Vault" for sessions with sub-connections

avatar
avatar
avatar

Hi Devolutions Team

I just wanted to confirm that the bug is finally fixed with 2023.2.22.0. I was a bit surprised that this bugfix was noted as a new feature, as we clearly use this function since many years.

I hope the time that it took to fix this function isn't the new normal. I reported quite some bugs in the past and got always good response times and timely fixes. I was a bit suprised that it took so long this time...

Thanks and best regards

2023.1.10 seems breaking "Move to Vault" for sessions with sub-connections

avatar
avatar
avatar

Hi, any idea when a fix will be available?

Thank you and best regards

2023.1.10 seems not listing references for sub entries

avatar
avatar
avatar
avatar

I can confirm the fix.

Thank you and best regards!

2023.1.10 seems not listing references for sub entries

avatar
avatar
avatar
avatar

After upgrading RDM from 2022.3.29.0 to 2023.1.10 only references for normal entries are shown in the "Referenced By" tab of the overview. References to sub entries aren't listed anymore.

Steps to reproduce

  • Create Username/Password entry

  • Create Host entry, link credentials to Username/Password entry

  • Create another Host entry, create sub entry below this Host entry and ljnk credentials to Username/Password entry for this sub entry

  • Check "Referenced By" tab for Username/Password entry --> only the first Host entry is listed, the sub entry of the second Host entry is missing

Best regards

2023.1.10 seems breaking "Move to Vault" for sessions with sub-connections

avatar
avatar
avatar

Thanks for the fast response and testing! So we will avoid moving stuff between vaults until a fix is available...

Best regards

2023.1.10 seems breaking "Move to Vault" for sessions with sub-connections

avatar
avatar
avatar

We use RDM with MSSQL DB and just updated from 2022.3.29.0 to 2023.1.10. While moving entries with sub-connections between vaults, only the base connection get's transferred. Sub-connections remain in the source vault. This definitely wasn't the case with the old version.

Can you reproduce this behavior?

Best regards

Variable resolution bug for in (at least) Host Sessions

avatar
avatar
avatar

Hi RDM Team,

I observed a bug in Host Sessions based on Variables if the "Continuous Ping" is used. Nearly all our Host Session are defined as "$NAME$.$COMPANY_DOMAIN$".

Beginning with at least 2021.2.11.0 and also with 2021.2.15.0 the variable isn't resolved when the ping is started. Instead the following is shown:

"Port Scan" and "Trace Route" seem also be affected. Other Tools like "Event Viewer", "Check is Online" and "Check Host Uptime" work as expected.

The last working version that we used was 2021.1.41.0.

Best regards

Check for Updates setting ignored

avatar
avatar
avatar
avatar
avatar

Since upgrading to 2021.2.11.0 I haven't seen the notification anymore.

Thanks for the quick fix of the hiccup!

Best regards

Check for Updates setting ignored

avatar
avatar
avatar
avatar
avatar

The problem wasn't that the update was being checked, but that the message appeared despite it not being checked.

If there is really no check, than it is ok for sure. I haven't traced the network traffic... ;)

Best regards

Check for Updates setting ignored

avatar
avatar
avatar
avatar
avatar

Thanks for following up and opening a ticket for fixing this behavior in the future! But I must admit that I have some doubts if this is the right way to fix this problem. The question for me is: Why are updates being checked for in the background, even though updates are disabled?

Or more to the point: Where to disable these background update checks, if the GPO and RDM settings only disable menus and update checks at startup? Or did I missed something?

Best regards

Check for Updates setting ignored

avatar
avatar
avatar
avatar
avatar

Thanks for your answer. It took me a bit to verify, but now I'm pretty sure, that configuring this GPO doesn't work as intended. Now after quite some time (one or two days of having RDM open) this popup appears:

This happens with these two GPOs set:

If I remove the GPO settings, the update window is back after having RDM open for a day or two...

Best regards

Check for Updates setting ignored

avatar
avatar
avatar
avatar
avatar

Dear Devolutions Team, it seems like there is a change in behavior at least in Version 2021.1.41.0, where the "Check for Updates" checkbox is ignored. Despite there no tick in the checkbox this version started to pop up from time to time with messages regarding newer versions available.

Was there another option added to toggle this message or is it a bug? In an environment, where RDM is distributed automatically, this is rather annoying...

Best regards

"Referenced by" behavior differs for credentials and asset contacts

avatar
avatar
avatar
avatar
avatar

PS: Where is the "mark as resolved" button in the forums? 😉

"Referenced by" behavior differs for credentials and asset contacts

avatar
avatar
avatar
avatar
avatar

Hi Devolutions Team, the issue seems to be successfully resolved in 2021.1.40.0.

Thank you for your support and keep up the good work!

Best regards

"Referenced by" behavior differs for credentials and asset contacts

avatar
avatar
avatar
avatar
avatar

If credential entries are referenced by normal session entries or sub connections of an entry, they are either way correctly shown in the "Referenced by" section of the linked entry.

For Contacts, that are linked in the Asset --> Contact --> Reference area, this only works for normal sessions. Contact references defined on sub connection level aren't resolved in the "Referenced by" section of the linked entry.

I'm quite unsure about the behavior in the past, but I think this should have worked with older versions. Tested version is 2021.1.35.0...

Is this expected behavior or a bug?

Best regards

Sign *.rdp connection files

avatar
avatar
avatar

I don't know if such functionality exists yet in RDM, but is there a way to automatically sign the on the fly created RDP connection files?

The benefit of signed RDP files is that there would be no untrusted publisher message on connection launch of external RDP sessions.

The requirement would be that every RDM user has to have an appropriate certificate in his private or machine certificate store and RDM has to know the fingerprint to get the connection file signed with rdpsign.exe.

The process is described here: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/rdpsign

So either a global certificate could be used for all administrators of a company, that has to be in place on all administrator workstations or maybe a personal certificate for every user could bey used - but I think thats much harder to handle as RDM has to use a different certificate fingerprints, so that the appropriate fingerprint is used for rdpsign.exe.

It would be great to see such functionality, or did I miss another way to get rid of the untrusted publisher messages?

Best Regards

Devolutions Web Login Central Settings Managament

avatar
avatar
avatar

Thank you for verification and forwarding the the request to engineering! It would be nice to see this feature at least for the chrome version, but I can imagine that this could be hard to accomplish for all browsers...

Best regards

Devolutions Web Login Central Settings Managament

avatar
avatar
avatar

Yes, thats the point... ;)

Devolutions Web Login Central Settings Managament

avatar
avatar
avatar

Is there a way to configure the Web Login Settings centrally? For example Chrome has it's won API for this:

https://www.chromium.org/administrators/configuring-policy-for-extensions

The Devolutions Web Login Documentation doesn't mention anything on this topic...

Best regards

1 - 25 of 36 items