Problems with Proxy Tunnel (HTTP) authentication when called from SSH Session / SSH Tunnel

Backlog

Problems with Proxy Tunnel (HTTP) authentication when called from SSH Session / SSH Tunnel

avatar

Hi All,

We need to connect over a HTTP Connect proxy in order to access remote hosts by ssh.

As far as I understood this correct, I need to create a Proxy Tunnel, set it for Proxy Type HTTP and either mark as being used with SSH Shell, or enter some dummy data in Local Host / Remote host part.

Then, when creating the SSH Session / SSH Tunnel, In Proxy tab I choose Link and point to the Proxy Tunnel created.

There is however a problem with authentication - it seems, that despite setting the Proxy Tunnel to use "My personal credentials" it is not being used when called from SSH Session / SSH Tunnel. When I start the Proxy Tunnel directly (after removing mark for it to be used by SSH and entering some meaningful data for remote / local host) it starts and authenticates correctly. I can confirm that in proxy logs. When it is called by the SSH Session however, no authentication is performed, and my HTTP Proxy rejects this request.

Even more interesting is, that when I set proxy mode in SSH Session / SSH Tunnel not to Link but to Custom, there is no option to lookup credentials in user vaults or use "my personal credentials" but I have to enter a particular user/password that is saved and used for all users. Those entered credentials are used for auth correctly. It would be enough could I choose there to get the credentials from somewhere not need to enter them directly, as each user has to use his own credentials. I tried with $TOOL_PASSWORD$ and similar, but this did not work (even after marking to allow password in variables).

And last but not least - Web sessions (using builtin Chrome) not even support HTTP proxy out of the box, with the possibility to authenticate from chosen source of credentials, but also do NTLM based Proxy Authentification.

I have found out, that HTTP Proxy Tunnel can only perform Basic Authentification which is not very safe nowadays. Do you plan to add support for NTLM there as well?

All Comments (32)

avatar

Hello,

Thank you for reaching out to us regarding this,

I have a few questions which you can hopefully answer.

  • Which version of RDM are you using?

  • Which type of data source are you using?

I'm wondering if you could provide me with some screenshots of your current configuration? Feel free to blur out any sensitive information.

Regarding your last point, I would need to discuss this with our engineering department to confirm if that is something that is planned.

Best regards,

Samuel Dery

avatar

Hi,

where

This is RDM 2023.1.26.0 64-bit with Data Source based on Microsoft SQL Server.

As for screenshots, this is the Proxy Tunnel entry:

where 10.200 is the Proxy IP, and 10.160 is the jumpserver IP where I connect via SSH to. When clicked directly, Authentication happens without problems using my personal credentials:

Now this is the SSH Tunnel entry (it shows more verbose error messages as SSH Session):

and its proxy card:

When I try this connection i get following error:

I should not be asked for proxy password, and regardless what I enter it does not authenticate. Probably it not only cannot find the password, but also the username and therefore It cannot properly authenticate despite the fact, that the linked proxy entry works and has correct credentials specified.

As I have just the one jumpserver I would even prefer not to use an additional Proxy Tunnel entry, but fill the proxy details directly on the SSH Tunnel entry in Proxy card, but there is no option to use per-user changable credentials (like my personal credentials or personal vault lookup for specified text):

As you see - the credentials above are used to SSH Authentification, not Proxy authentification and the only way to pass credentials to proxy is to hardcode it in the entry meaning that every logged in user will use the same credentials which is not acceptable. If there were an option to use logged-in OS Credentials, ideally ober NTLM this would be great. Whatever I enter here is used correctly via Basic Auth but this does not match our use case, where proxy authentification has to be done with personal user of currently logged in user. I tried to use Custom as on above screenshot with diverse $xxx_USERNAME$ / $xx_PASSWORD$ but none of them worked either.

I hope this explains the situation a bit more precise.

avatar

Hello,

Thank you for your reply and for the screenshots,

I see, in that case, I believe using User specific settings would solve this issue, we have the following knowledge base article regarding this:

https://docs.devolutions.net/rdm/windows/commands/edit/setting-overrides/specific-settings/

This would allow each user to have their own custom credentials set on the entry directly without impacting others, could you try this and let me know if it works as expected?

Best regards,

Samuel Dery