Using different sock proxy port in templates

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,

Hi Carl,

I hope i understand you suggestion correctly.

So i on ie my SSH terminal template link to SOCKS proxy configuration (which then need to be in the systemvault as that the only way i can select it in the list)

I then have a SOCKS proxy configuration in the systemvault

This i can get to work, but i do not see how i can have a template for ie SSH terminal to use a different SOCKS proxy configuration based on which vault im lunching it from.
But unless i miss something here, then i still do not see how configure.


Also which might be importen information, we are using the session type "host" with templates attached.
Like show here, the reason for that is that for some of customere we would start to use way to many session if we had ie SSH terminal as a standalone session type.
With our largest vault we have around 11.000 entries with this setup. (just as FYI about why we have it configured like this)