david

Good day Devolutions,

Would it be possible to change how the credentials are injected in connection?

We have the following situation:

We finish our daily work. And we logout from our connections. But RDM stays open - with all of the tabs in disconnected state (like below).

Basically, when we are back in office tomorrow, if we press "Connect", it attempts to log us in with "old" password from previous day since our admin accounts are rotated every 24 hours by Delinea Secret server (and this credential type we are using to connect).

Would it be possible that, when we press "Connect" it fetches "latest" credentials?

Hi Francois,

That would be even better!

Hello

We have 2 gateways in a farm.

We execute connection which is using gateway as a farm. We note down that connection is established via gateway #1.

We stop the Gateway service on the gateway #1. RDP connection is dropped. We close the connection. We try to execute the same connection. It keeps trying to establish connection over the gateway #1, even though we several times close/re-launch the connection. It does not automatically change to establish connection over gateway #2 until the health check is triggered, or we manually trigger gateway scan through web UI.

Hi, do you think that this change from minutes to seconds will be released soon?

Sorry, perhaps i was a bit unclear.

"The idea is that users should be able to instantly reconnect in case of a gateway failure". - i've only meant, that the health check interval is too long, and user will not wait for 1 minute before trying to reconnect. They will send us a ticket instead.

But if the health interval could be reduced to 1-5 seconds, that should be satisfactory.

Good day,

Would it be possible to change the Gateway Health check interval?

Currently this is only possible in minutes, with lowest value of 1. It does not accept 0.XX values.

Idea is that users should be able to instantly reconnect - in case of failure of gateway.

Hi Hubert,

It is not optimal (as it would mean we need to redo entire vaults with thousands of entries) but it is a good backup plan.

According to Erica, there is an internal ticket opened in Devolutions to make Delinea Secret Server credentials editable in the DVLS web UI. This solution fits perfectly into our scenario.

Good morning Devolutions

As the subject implies, we found out that there is no way to put console password in the DVLS Console, if there is only Gateway installed in standalone mode.

This potentially gives access to the gateway configuration to other support teams - which are connecting to the same server.

Hi Hubert, sorry for a late response

Yeah, i can make the connection work with my "My personal credentials" and "My privileged account".

But "My personal credentials" and "My privileged account", is "one for all" use case? How would a user define different account lookup for different entries?

And what in case if the user needs to edit "My privileged account"? Where could he do that?

Hi Hubert, do you perhaps have a timeframe, when we could expect this to be implemented?

Hi Hubert, do you perhaps have a timeframe, when we could expect this to be implemented?

Thank you Hubert

Hi Hubert,

Exactly, user with RDM client is able to edit these credentials, but not in launcher. He is not able to edit these credentials in web interface as well. So basically these types of entries are unusable in Launcher.

Hi Hubert

That is exactly what we would need, thanks!

Hi Maxime,

We are using DVLS 2024.3.4.0

We have the following scenario:

Users need to use Server #1 as their point of entry to the infrastructure.

From there, they are able to connect to all other servers (Server #2, Server #3 etc). Server #1 has RDM client installed.

Connection entry to Server #2 is set to use Server #1 as jumphost with RDM jump.

Scenario

User has an RDM client installed on his workstation.

From his RDM client, he executes connection to Server #2.

This connects him to Server #1. And triggers RDM jump - basically opens RDM client on Server #1, and then connects him to server #2.

This basically opens 2 RDM clients, and the user is seeing 3 windows start menus. Which can be very confusing at times.

Are there any possibilities to change this in the future?

So that RDM jump executes in "background", without end user noticing it? So that he would only have 1 RDM client open (on his workstation)?

Currently a user which only has launcher license assigned - is unable to add/edit credentials in the vault, if the credentials are made for Delinea PAM solution (we also noticed others).

As all of our users are obliged to have their accounts onboarded to Delinea PAM, with autorotation of passwords, this makes Launcher not a feasable solution. In every other aspect - Launcher is perfect for their needs.

Are there any plans to improve this in future versions of the Launcher?

Are there any plans to have the option to create a custom installer for the Launcher (as to what is currently available in the RDM client)? This would drastically simplify the deployment and update process of the launcher client on a large scale

Good morning Devolutions

We have different users - business who are using Devolutions Launcher, and IT admins who are using RDM client. We are finding it difficult to manage licenses. At the moment, this is only possible per user. This is causing a lot of manual overhead, since we need to assign each user license manually (depending on their role).

Also, when the user is offboarded, cleanup is also manual.

We would ike to have possibility to use Active directory groups - to assign RDM and Launcher licenses separately. And also to remove license automatically once the user is no longer a member of the group.

As we have several administrators of RDM, we would like to have additional information in the syslog.

When someone edits an entry, the log is generated, but it does not specify, what information/field was changed.

When we export entire vault (File -> Export -> Export vault (.rdm) ), there is no log generated.

Could this information be added to the syslog?