[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Najib Aouni updated GUACAMOLE-1836:
-----------------------------------
    Description: 
Windows allows you to redirect WebAuthN requests using the 
"redirectwebauthn:i:value" parameter. See: 
[https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/rdp-files#device-redirection]

This way you can use a locally attached FIDO2 security key or wearable inside a 
RDP connection where WebAuthN is triggered improving security even further 
without relying on non-phishing resistant 2fa such as TOTP inside a Guac 
session.

 

  was:
Windows allows you to redirect WebAuthN requests using the 
"redirectwebauthn:i:value" parameter. See: 
https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/rdp-files#device-redirection

This way you can use a locally attached FIDO2 inside an RDP connection where 
WebAuthN is triggered improving security even further without relying on 
non-phishing resistant 2fa such as TOTP inside a Guac session.

 


> Add WebAuthN redirection for RDP connections
> --------------------------------------------
>
>                 Key: GUACAMOLE-1836
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1836
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-common
>            Reporter: Najib Aouni
>            Priority: Trivial
>
> Windows allows you to redirect WebAuthN requests using the 
> "redirectwebauthn:i:value" parameter. See: 
> [https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/rdp-files#device-redirection]
> This way you can use a locally attached FIDO2 security key or wearable inside 
> a RDP connection where WebAuthN is triggered improving security even further 
> without relying on non-phishing resistant 2fa such as TOTP inside a Guac 
> session.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to