> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/keeperpam/privileged-access-manager/remote-browser-isolation/setting-up-rbi/fido2-security-keys.md).

# FIDO2 Security Keys

Using a FIDO2 Security Key with RBI

## Overview

Keeper's Remote Browser Isolation (RBI) now supports hardware security key passthrough, allowing users to authenticate with FIDO2-compatible devices (such as a YubiKey) while browsing through an RBI session. This means users who are required to authenticate with a hardware key on enterprise sites like Microsoft Azure can do so seamlessly without leaving the isolated browsing environment.

## How it Works

When a user accesses a website through an RBI session that requires hardware key authentication, Keeper relays the WebAuthn request from the remote browser back to the user's local browser. The user's physical hardware key is detected locally, and the authentication is completed as if they were browsing directly — keeping the session fully isolated while preserving the native authentication workflow.

## Requirements

1. **Browser** — This feature is currently supported on **Google Chrome only**. Firefox, Safari, and Brave are not supported at this time.
2. **Keeper components:**

* Keeper Vault 18.6.0 or later
* An updated Keeper Gateway

3. **Operating System Setup —** Before hardware key passthrough will work in an RBI session, your machine must be configured to allow it.

* **macOS:** Open Terminal and run the following command, replacing the URL with the address you use to access the Keeper Vault, **NOT** the URL for the site you access via RBI:

```bash
defaults write com.google.Chrome WebAuthenticationRemoteDesktopAllowedOrigins -array "https://your-vault-url.com"
```

* **Windows:** Open a terminal with **administrator privileges** and run the following command, replacing the URL with the address you use to access the Keeper Vault, **NOT** the URL for the site you access via RBI:

```powershell
reg add "HKLM\SOFTWARE\Policies\Google\Chrome\WebAuthenticationRemoteDesktopAllowedOrigins" /v 1 /t REG_SZ /d "https://your-vault-url.com" /f
```

{% hint style="warning" %}
This registry change requires administrator privileges. Contact your IT administrator if needed.
{% endhint %}

## Troubleshooting

**Hardware key is not detected**

* Confirm you are using Google Chrome as your browser
* Verify the configuration uses the correct Vault URL
* Confirm the hardware key works outside of the RBI session by testing it directly in the Keeper Vault

**PIN prompt does not appear**

* This is typically resolved by a full system reboot
* Ensure the registry or preference setting is applied correctly for your environment

## Supported Environments

| Environment      | Supported       |
| ---------------- | --------------- |
| macOS + Chrome   | ✅ Yes           |
| Windows + Chrome | ✅ Yes           |
| Firefox          | ❌ Not supported |
| Safari           | ❌ Not supported |
| Brave            | ❌ Not supported |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://newdocs.keeper.io/en/keeperpam/privileged-access-manager/remote-browser-isolation/setting-up-rbi/fido2-security-keys.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.