devolutionssyenite

Same on 2024.1.28.0 as well.

2024.1.27.0

Win 11 22h2

devolutions server

yes

no

When searching all vaults in the search box, the "enter" shortcut to open the searched item does not work. When turning off the all vault search, the enter key again works. Is there a setting to change this, or is this a bug? Thanks!

I opened a ticket and responded to you there.

I am trying to setup a trial of Devolutions Server and am having some issues. SSO is configured per documentation, but getting a "Could not Connect" error, manual sign on appears to work, but then get an error that we have no RDM licenses. I added the RDM licenses to the server as well for our trial. This is a brand new blank database, separate from the production SQL one we are currently using in production for RDM only.

Edit: I found it just isn't automatically assigned licenses and resolved the license portion of my issue. Now I get a connection error for sso or manual, I see some http request timeout errors in the application logs.

The one missing for me is ability to add a shortcut to Open (Select Credentials). I have too many different credentials for different domains. The select credentials option opens my personal vault which is linked to passwordstate entries for me and I select from there. It would be nice to have a keyboard shortcut for this option, but I don't see it in the list of available keyboard shortcut options in the settings.

More complementary to add data to existing entries. It has a full API so we may also look ourselves. I just found your powershell module, it appears I can edit entries with it, so we will have to see what we can put together.

We use the Snow Agent in our environment which gathers information on all systems for us. It would be great to be able to sync this information with server entries to populate metadata fields such as the connections generated from the vmware sync.

Completely understood, and the point was just that the more metadata in any of them is helpful for all the sorting, rules, templates, etc. Another good one for Vmware will be to pull the machine fqdn, connect via IP is not preferred, but I need FQDN as I have multiple domains.

Those docker and linux servers are part of the reason I want this! It will make it much easier to sort to different folders for ssh vs rdp vs other with the additional data. This is really the reason we need it!

I would say any and all data/tags are helpful. Including in the AD sync as well. The more information I can populate automatically the better. My AD information is up to date as are all my vmware tags, os information, etc. Any of this metadata helps sort and apply different templates/rules, for any of the synchronizers, not just this one.

It's unfortunate this was never implemented. Not just tags, but OS type and other vm information would be very useful because then I could set some connections to SSH and others to RDP based on OS type or other criteria. Right now it's very basic and just syncs. It works, but it could be so much more useful!