--- title: "Default FIDO2 provider" slug: "fido2-provider-devices-v7-0" description: "Explore FIDO2 device authentication with AppGate ZTNA, featuring touch, PIN, and fingerprint options for secure user interactions and privacy." tags: ["FIDO2 Devices"] updated: 2026-06-05T19:17:40Z published: 2026-06-05T19:17:40Z canonical: "support.appgate.com/fido2-provider-devices-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Default FIDO2 provider FIDO2 is an evolving standard with a range of manufacturers and device types. Some devices require only touch, while others require touch and a PIN. More advanced ones include fingerprint recognition. AppGate ZTNA currently has the following limitations: - The intent is to support only touch and fingerprint (because no UI interaction is required). - On Windows, FIDO is handled by the operating system, so more advanced, UI-interactive features are available, including a PIN. Many FIDO2 device manufacturers have companion apps available. You can use these apps to identify device types and version information, and to configure options such as using a PIN. FIDO2 devices might work out of the box, or they might require changes—such as disabling the PIN—before you use them with AppGate ZTNA. You can enable FIDO2 devices separately for different apps, such as AppGate ZTNA. This should mean it is possible to use the same FIDO2 device for user device authentication (see [Secure password-less sign-in for your Microsoft account using a security key or Windows Hello](https://www.microsoft.com/en-us/microsoft-365/blog/2018/11/20/sign-in-to-your-microsoft-account-without-a-password-using-windows-hello-or-a-security-key/)) and for a user interaction using AppGate ZTNA. > [!NOTE] > **NOTE** > > Not all use cases are supported in AppGate ZTNA at this time. You cannot use FIDO2 for admin UI access. --- ## Initialization After setup, the user plugs a new FIDO2 device into the USB port when prompted. After initialization, the user response for a triggered user interaction is to touch the FIDO2 device. Initialization happens automatically the first time the FIDO2 device is used with AppGate ZTNA. The FIDO key creates a new credential key pair: the FIDO device retains the private key, and the public key is signed by the attestation key pair (model specific, not device specific) and sent to the AppGate ZTNA Controller. Authentication is achieved when the FIDO key sends a signed response (using the private key) to any subsequent challenge sent by the AppGate ZTNA Controller. The device’s private keys can be used only after the user unlocks them locally. The local unlock is accomplished when the user inserts the FIDO2 device and touches the button. The Controller associates the public key with the user, so the user needs that key in future because it contains the matching private key. The Controller does not care which key is used, only that a key pair exists for that user. Because the key is not necessarily bound to a user, it is possible for two users to share a key. This is an advantage when an AppGate ZTNA user has a local account and an LDAP account, which would appear as two different users to the system. In this case, the user could use the same FIDO key for both accounts. Authentications remains unique, because each account generates a unique key pair during initialization. This also means you can use the same key multiple times. For example, you can tie Google, O365, and one or more AppGate ZTNA instances to a single key. One of the FIDO principals is user privacy, so the attestation signing certificate is unique to a device model, not an individual device. If every device had a different attestation certificate, that certificate could be used to track and identify an individual across the different services where the FIDO key is used. ### Reinitializing In some circumstances, you may need to reinitialize the FIDO2 device. To reinitialize: 1. Go to the **FIDO2 Provider Devices** page (Usage > FIDO2 Provider Devices). 2. Select the Action button (![Three circular shapes stacked vertically on a dark background, selected to access a menu.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/three_dots.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A49%3A46Z&se=2026-11-21T22%3A49%3A46Z&sr=b&sp=r&sig=0TpekxVg%2BW2WAE9bc%2FFWrIu3Vd%2F5Q%2B4L%2BazMEhruwhU%3D)) next to the FIDO2 device you want to reinitialize and select *Remove device*. 3. When the user accesses the protected resource again, the initialization process is triggered again. --- ## The FIDO2 Provider Devices page The **FIDO2 Provider Devices** page (Usage > FIDO2 Provider Devices) lists all FIDO2 devices registered for MFA. > [!NOTE] > NOTE > > Not all FIDO2 device IDs and FIDO2 device names are shown, because some devices report these using nonstandard mechanisms. The **MFA Providers** page layout includes the following columns: - ***Username***. The username of the person using the FIDO2 device. - ***Identity Provider***. The identity provider of the user. - ***FIDO2 Device ID***. The device ID of the FIDO2 device, if available. - ***FIDO2 Device Name***. The device name of the FIDO2 device, if available. --- ## Managing FIDO2 devices Use the action button—the three dots icon (![Three circular shapes stacked vertically on a dark background, selected to access a menu.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/three_dots.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A49%3A46Z&se=2026-11-21T22%3A49%3A46Z&sr=b&sp=r&sig=0TpekxVg%2BW2WAE9bc%2FFWrIu3Vd%2F5Q%2B4L%2BazMEhruwhU%3D)) to the right of each line item— to access the following option: - ***Remove device***. Removing a FIDO2 device allows it to reinitialize on the user’s device the next time the user accesses the protected resource.