[BUG] Shared RDP host with authType "none" does not prompt shared user for credentials

Title

Shared RDP host with authType "none" does not prompt shared user for credentials

Platform

Website - Other Browser

Server Installation Method

Docker

Version

2.7.1

CLI Installation Method

No response

CLI Version

No response

Troubleshooting

• I have examined logs and tried to find the issue
• I have reviewed opened and closed issues
• I have tried restarting the application
• I have checked open issues and ensured this is not a duplicate

The Problem

When an RDP host is configured with Auth Method: None, the host owner is correctly prompted to enter a username and password when starting the RDP session.

However, when that same host is shared with another Termix user, the shared user is not prompted for credentials. Termix attempts to establish the RDP connection without displaying the username/password prompt and the connection fails with:

Authentication failure (invalid credentials?)

The shared user can see the host and initiate the connection, so host sharing itself appears to be working.

This prevents using shared RDP hosts where each user should authenticate to Windows with their own credentials. The expected behavior is for a shared user to receive the same runtime credential prompt as the host owner.

A shared RDP connection does work when the host is configured with Direct authentication and a saved credential. This confirms that host sharing and RDP connectivity are functioning correctly. The issue appears specific to shared RDP hosts configured with Auth Method: None, where the shared user is not shown the runtime credential prompt.

Environment

• Termix 2.7.1
• Docker image: ghcr.io/lukegus/termix:latest
• Protocol: RDP
• Auth Method: None
• Security Mode: Any
• Termix users authenticated via LDAP

How to Reproduce

1. User A creates an RDP host and sets Auth Method to None.
2. User A connects to the RDP host. Termix correctly prompts for a username and password and the RDP connection works.
3. User A shares the RDP host with User B.
4. User B logs into Termix and opens the shared RDP host.
5. User B clicks Connect.
6. Termix does not display the username/password prompt.
7. Termix attempts the RDP connection and reports Authentication failure (invalid credentials?).

As a control test, change the same shared RDP host to Direct authentication with a saved credential. The shared user can connect successfully.

Expected behavior: User B should receive the same username/password prompt as User A, allowing User B to authenticate to the RDP host with their own Windows credentials.

Actual behavior: The credential prompt is skipped for the shared user and the RDP connection fails.

Additional Context

Setting a shared RDP connection to direct, with a saved credential, does work with a shared. user.

No response

No source files or tests are identified in the report. Start by reproducing the shared-user flow for an RDP host using Auth Method: None in the Docker installation, comparing it with the host-owner flow and the Direct-auth control case. Done means shared users receive a runtime username/password prompt and can connect with their own credentials.