mRemoteNG / mRemoteNG/mRemoteNG

How to: SSH Tunnel with SSO password --> With SHARE SSH CONNECTION option

Open
#2,034 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Need 2 check
Dominant language
C#
Stars
11.1k
Forks
1.6k
Avg merge
16h 58m
Merged PRs (30d)
55

Description

Hi,

I'm testing the last nightly build, and the "new" SSH TUNNEL (jump host) functionality is a must have. Thank you for it. However, I have one suggestion to improve it:

  • The idea is to add a new option called "share tunnel password". This implements the functionality to store the typed password the fisrt time it's used. And for all new connections using the same tunnel, the password of the jump host will be reused... without typing it again. This will be similar to a SSO (Single Sign-On) functionality. And this improves a lot the usability when you need to access to a lot of servers/machines from outside using the jump host.

I hope you want to implement this.
Regards.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the SSH TUNNEL (jump host) connection handling in the mRemoteNG desktop application and review how connection credentials are currently managed. Define the security and scope of reusing the first typed jump-host password, then verify that the new share-tunnel-password option works across subsequent connections without requiring repeated entry.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
authentication, desktop, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.