Windows 10/11 Wired 802.1X (EAP-TEAP): How to trigger user authentication after an RDP logon without disconnecting the Ethernet interface?
Scenario
We are deploying wired IEEE 802.1X authentication in enterprise environments using the native Windows supplicant (Wired AutoConfig / dot3svc) and Aruba ClearPass as the RADIUS authentication server.
Our authentication configuration uses:
Operating systems: Windows 10 and Windows 11.
Network access: Wired Ethernet (IEEE 802.1X).
Supplicant: Native Windows 802.1X supplicant (dot3svc).
Outer EAP method: EAP-TEAP.
Inner authentication: EAP-TLS for both machine and user authentication (machine/user identity chaining).
RADIUS server: Aruba ClearPass.
Network infrastructure: Aruba AOS-CX switches.
Identity infrastructure: Active Directory and an internal Microsoft CA issuing machine and user certificates.
Our objective is to authenticate both the computer and the currently logged-in domain user, allowing the network access control solution to apply authorization policies based on both identities.
Problem description
We have identified an issue when a user establishes a Remote Desktop (RDP) session to a Windows computer that is already connected to the wired network and has successfully authenticated through 802.1X using machine authentication.
When the RDP session is established, the physical Ethernet interface remains connected and its link state does not change.
Windows does not appear to automatically initiate a new EAPOL/TEAP authentication exchange following the RDP logon. More importantly, even when we explicitly trigger 802.1X reauthentication from the AOS-CX switch to which the computer is connected, Windows does not provide the user authentication component of the TEAP exchange, despite the RDP user already being logged in.
As a result, ClearPass continues to receive only the machine authentication identity, rather than both the machine and user identities.
Consequently, the network access control solution cannot identify the user connected through RDP or apply the corresponding user-based authorization policies.
We have observed this behaviour in multiple enterprise environments using Windows 10 and Windows 11.
What we would like to achieve
We would like Windows to provide the currently logged-in user's authentication identity during a new EAP-TEAP exchange initiated after an RDP logon, including when the exchange is explicitly triggered by the network switch.
Ideally, this should be possible without physically disconnecting and reconnecting the Ethernet interface.
Questions
Is this a known limitation of the native Windows wired 802.1X supplicant when using EAP-TEAP with machine/user identity chaining over RDP sessions?
Is there a supported way to make Windows provide the logged-in user's EAP-TLS authentication identity when a new 802.1X authentication exchange is initiated following an RDP logon?
Are there any supported configuration options, registry settings, Group Policies, commands or APIs that can control or trigger this behaviour?
Is there a recommended workaround that would allow us to retain machine/user identity chaining in this scenario?
Troubleshooting and documentation reviewed
We have found the following Microsoft documentation, which appears to describe a related limitation:
KB 2820847 – 802.1x user authentication fails when an RDS connection comes in
However, this documentation appears to address a different authentication configuration, and we would like to understand whether the same limitation applies to EAP-TEAP with machine/user identity chaining and EAP-TLS.
We have also investigated possible workarounds involving Windows logon events and PowerShell scripts, but would prefer to use a native, supported Windows mechanism if one exists.
Expected outcome
Our goal is to retain EAP-TEAP machine/user identity chaining while ensuring that the network access control system can identify users connecting through RDP.
Reverting to machine-only authentication would eliminate the issue but would also remove the user-level visibility and authorization granularity that we are trying to achieve.
Any information about known limitations, supported configuration options or practical workarounds would be greatly appreciated.
Scenario
We are deploying wired IEEE 802.1X authentication in enterprise environments using the native Windows supplicant (Wired AutoConfig / dot3svc) and Aruba ClearPass as the RADIUS authentication server.
Our authentication configuration uses:
Operating systems: Windows 10 and Windows 11.
Network access: Wired Ethernet (IEEE 802.1X).
Supplicant: Native Windows 802.1X supplicant (dot3svc).
Outer EAP method: EAP-TEAP.
Inner authentication: EAP-TLS for both machine and user authentication (machine/user identity chaining).
RADIUS server: Aruba ClearPass.
Network infrastructure: Aruba AOS-CX switches.
Identity infrastructure: Active Directory and an internal Microsoft CA issuing machine and user certificates.
Our objective is to authenticate both the computer and the currently logged-in domain user, allowing the network access control solution to apply authorization policies based on both identities.
Problem description
We have identified an issue when a user establishes a Remote Desktop (RDP) session to a Windows computer that is already connected to the wired network and has successfully authenticated through 802.1X using machine authentication.
When the RDP session is established, the physical Ethernet interface remains connected and its link state does not change.
Windows does not appear to automatically initiate a new EAPOL/TEAP authentication exchange following the RDP logon. More importantly, even when we explicitly trigger 802.1X reauthentication from the AOS-CX switch to which the computer is connected, Windows does not provide the user authentication component of the TEAP exchange, despite the RDP user already being logged in.
As a result, ClearPass continues to receive only the machine authentication identity, rather than both the machine and user identities.
Consequently, the network access control solution cannot identify the user connected through RDP or apply the corresponding user-based authorization policies.
We have observed this behaviour in multiple enterprise environments using Windows 10 and Windows 11.
What we would like to achieve
We would like Windows to provide the currently logged-in user's authentication identity during a new EAP-TEAP exchange initiated after an RDP logon, including when the exchange is explicitly triggered by the network switch.
Ideally, this should be possible without physically disconnecting and reconnecting the Ethernet interface.
Questions
Is this a known limitation of the native Windows wired 802.1X supplicant when using EAP-TEAP with machine/user identity chaining over RDP sessions?
Is there a supported way to make Windows provide the logged-in user's EAP-TLS authentication identity when a new 802.1X authentication exchange is initiated following an RDP logon?
Are there any supported configuration options, registry settings, Group Policies, commands or APIs that can control or trigger this behaviour?
Is there a recommended workaround that would allow us to retain machine/user identity chaining in this scenario?
Troubleshooting and documentation reviewed
We have found the following Microsoft documentation, which appears to describe a related limitation:
KB 2820847 – 802.1x user authentication fails when an RDS connection comes in
However, this documentation appears to address a different authentication configuration, and we would like to understand whether the same limitation applies to EAP-TEAP with machine/user identity chaining and EAP-TLS.
We have also investigated possible workarounds involving Windows logon events and PowerShell scripts, but would prefer to use a native, supported Windows mechanism if one exists.
Expected outcome
Our goal is to retain EAP-TEAP machine/user identity chaining while ensuring that the network access control system can identify users connecting through RDP.
Reverting to machine-only authentication would eliminate the issue but would also remove the user-level visibility and authorization granularity that we are trying to achieve.
Any information about known limitations, supported configuration options or practical workarounds would be greatly appreciated. Thank you in advance!