davidneuhauser

Hello,

im not sure if this is a bug report or a feature request.

We have the issue that RDM disregards the port of a connection if its using a proxied connection over delinea Secret Server.

so whatever port we specify here, in this case 3001, is disregarded and it always uses the standard 22.

This on the other hand works directly in SecretServer

Would it be possible to fix/add this to RDM?

Best regards,

David

Hey, i just wanted to check if there is any progress or an eta on this?

Regrads,

David

Hello,

currently the Delinea Secret Server entry supports two Resolving modes:

Injection -> never proxy

Connection through proxy -> force proxy and fail on all connections using a delinea secret that are not RDP or SSH

But we would like to be able to use our Secret Server for all entry types, like Websites and SFTP,... and use the proxy only for those supported.

My request would be an additional Resolving mode:

Connection through proxy if available -> use proxy on all connection types that support it, use injection otherwise

Thanks in advance!

David

Hey,

I just wanted to check in, if there are any updates on this matter?

Best regards,

David

Our Company is currently using the Delinea Proxy SSH and RDP sessions. It would be great to be able to also use SFTP via the Proxy in RDM.

Out Company is currently using the Delinea Proxy SSH and RDP sessions. It would be great to be able to also use SFTP via the Proxy in RDM.

We are using powershell to automate changes in our RDM Database. We found, that despite manually creating a DelineaProxy Connection, some of the objects entries, for example host, are always empty in the powershell object.

Also altering the entry in the ps object, again for example host, and then setting the session does not actually change anything in RDM.

We are using pwsh 7.5.0

devolutions.powershell 2025.1.0

and we updated the db-schema already

If any further information is required, please let me know.