Using RSA Token for RDP instead of Windows password

Hello @Johnny

RSA SecurID authentication for RDP isn't something that can be enabled through a Windows registry change or Group Policy alone. RDP delegates authentication to Windows, so to replace (or supplement) Windows password authentication with RSA, you need an authentication integration that plugs into the Windows logon process.

Depending on your environment, the supported approaches typically include:

• Installing the RSA Authentication Agent for Microsoft Windows, which integrates RSA SecurID with Windows logon and Remote Desktop.
• Using Network Policy Server (NPS) with the RSA Authentication Agent for NPS if you're enforcing MFA through Remote Desktop Gateway (RD Gateway) rather than on each Windows server.
• If you're using Microsoft Entra ID, consider Microsoft Entra MFA with RD Gateway or other supported MFA solutions instead of replacing the Windows credential provider directly.

A few questions that will help narrow this down:

• Are users connecting directly to the Windows Server via RDP, or are they connecting through an RD Gateway?
• Are you using RSA SecurID Authentication Manager (on-premises) or RSA ID Plus (cloud)?
• Is your goal to replace the Windows password entirely, or to require an RSA token as a second authentication factor?

Those details will determine which integration method is supported. Simply configuring local policies or registry settings won't cause the Windows logon screen to prompt for an RSA token unless the appropriate RSA authentication components are installed.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.