Devolutions ForumDevolutions Forum

Using different sock proxy port in templates

Using different sock proxy port in templates

avatar
kll

Hi,

I have a setup where i have a vault per customer.

In each vault we have a SSH VPN like this (including customer specific gateway config to connect)

I then have a customer specific template ie for ssh where i have the socks proxy configured

My question is then, would it be possible to somehow, have it so that i have the "proxy VPN" entry in the vault for creating the proxy like i have now.

And then only have 1 SSH template which i can use for all ?


I tried briefly to use dynamic port on the proxy entry, but i could not see a way to use the $DYNAMIC_PORT$ variable in the template.
I also tried to create a variable in the vault with the customer specific port, but i then again ran into not being able to use it.

I even tried to export the template and replace the port with the variable in the .rdm file, but then RDM do not want to import it.


Do you have any suggestions for a way to achive this ?

a4f75d10-9496-45ee-9646-002640a6ba49.png

f4c3f293-bef3-4932-9843-fc927608f40c.png

All Comments (1)

avatar
Carl Marien

Hello,

Instead of using a custom SOCKS proxy configuration directly in the template, we would recommend using a Link entry and linking it to the appropriate Proxy Tunnel entry.
This way, the template can stay generic, while the linked proxy/tunnel entry handles the customer-specific connection details. The VPN / Tunnel / Gateway entries can also be created under the System Vault, which allows them to be shared across different vaults when needed.

Also, as a side note, having one vault per user is generally not a structure we would normally recommend. Vaults are usually better organized by team, customer, environment, or permission boundary, depending on the use case.

Best regards,

Carl Marien