RDCMan: Support Idira PAM direct connections using cookie-based RD Gateway authentication
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.
- Dominant language
- No language data
- Stars
- 598
- Forks
- 280
- Avg merge
- 5h 23m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MicrosoftDocs/sysinternals
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
MicrosoftDocs/sysinternals#1027 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MicrosoftDocs/sysinternals#949 · 2 comments · 5 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 56/100
MicrosoftDocs/sysinternals#1029 ·
-
RDCMan 3.23 bug: smart card logon fails after reopening a saved .rdg (works in newly created file)Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MicrosoftDocs/sysinternals#1028 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
MicrosoftDocs/sysinternals#1024 · 1 comment · 1 reaction ·
All issues in MicrosoftDocs/sysinternals
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
longbridge/gpui-kit#4031 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
milind-soni/OpenMausBot#6495 ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
telegramdesktop/tdesktop#31653 ·
Maintainers usually reply within 1 day
-
Windows: file links in chat open the browser instead of locating the file in the workspace file treeOpenstatus: triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
WhiteTowerAI/ohmygame#972 ·
Maintainers usually reply within 1 day