RDCMan: Support Idira PAM direct connections using cookie-based RD Gateway authentication

Open
#1,030 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
desktop

Research direction

The issue does not name source files, tests, or entry points. Start by locating RDCMan’s Gateway Settings dialog, configuration persistence, and connection setup paths, then check how they handle gateway attributes and secrets. Done means the listed cookie authentication settings can be configured per connection, saved, and applied, with the access token kept out of logs and errors.

Written by the indexing model from the issue text.

Description

I would like to manage Idira PAM DirectConnections in RDCMan instead of opening the RDP files generated by Idira separately.

A working Idira-generated RDP file uses the following RD Gateway settings:

gatewayhostname:s::443
gatewayaccesstoken:s:secureaccess
gatewaycredentialssource:i:5
gatewayusagemethod:i:1
gatewayprofileusagemethod:i:1

The current Gateway Settings dialog does not expose all of these settings. In particular, it does not provide a way to configure cookie-based gateway authentication using gatewaycredentialssource:i:5, or to set the associated gatewayaccesstoken and usage-method values.

Could RDCMan allow these gateway attributes to be configured per connection in the Gateway Settings dialog, saved in the RDCMan configuration, and applied when establishing the connection? This would allow users to manage Idira PAM DirectConnections directly in RDCMan.

The gateway access token or value should be handled securely and not exposed in logs or error messages.

image
Dominant language
No language data
Stars
598
Forks
280
Avg merge
5h 23m
Merged PRs (30d)
5

Getting set up

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.

More from MicrosoftDocs/sysinternals

All issues in MicrosoftDocs/sysinternals

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.