Security key not recognised over USB, NFC, or tap during sign-in

TL;DR — If your security key is not recognised, the most common cause is the browser or device not actually talking to the key: try a supported browser, plug the key directly into the device instead of a hub, unlock the screen, and retry from the browser's sign-in prompt instead of a password manager pop-up. If the key still is not offered, check whether the key was ever registered on your account and whether USB/NFC access is blocked by your device settings or company policy. Reading time: ~6 min

The scenario

It is a normal Tuesday afternoon and you are trying to sign in to your agency portal, client dashboard, or SSO (single sign-on) page before a meeting. You enter your username and password, the page asks for your security key, and then nothing useful happens: plugging the key in does not trigger a prompt, tapping it on your phone does nothing, or the browser says it cannot find a compatible device. You try a different USB port, maybe refresh once or twice, and now you are wondering whether the problem is the key, the browser, your laptop, or your account. You need a quick way to tell which one it is without guessing.

Symptoms

• The sign-in page shows messages such as:
  • "No compatible security key found"
  • "Insert your security key and try again"
  • "Touch your security key"
  • "This browser does not support security keys"
  • "We couldn't verify your identity with that security key"
  • "Security key authentication failed"
• Plugging the key into USB causes no prompt, no light, or no vibration.
• Tapping the key on a phone over NFC (near-field communication, short-range wireless tap) does nothing.
• The browser opens a passkey/password manager prompt instead of asking for the physical key.
• The key works on one device or browser but not another.
• The key is detected by the operating system, but the website still says no registered key is available.
• On managed work devices, USB accessories or security keys are blocked by policy.

Likely causes

Step-by-step diagnosis

[Sign-in Page] ---- 1. prompt for key ----> [Browser]
[Browser] ---- 2. WebAuthn request ----> [OS]
[OS] ---- 3. talk to USB/NFC ----> [Security Key]
[Security Key] ---- 4. touch/PIN ----> [OS]
[OS] ---- 5. signed response ----> [Browser]
[Browser] ---- 6. complete login ----> [Account]

1. Retry in a supported browser and force the physical-key option
   Use one of these first: Chrome, Edge, Firefox, or Safari, updated to the latest version. On the sign-in page, if you see a choice such as "Use another method", "Try another way", or "Use security key", click that instead of accepting a passkey prompt from a password manager.
   This is your problem if: the key works in one browser but not the original one, or works only after choosing "Use security key" manually.
   Jump to: Fixes → Browser or sign-in flow is not using the security key correctly

2. Remove simple connection issues
   For USB keys: unplug the key from any dock, hub, monitor, keyboard, or adapter and plug it directly into a built-in USB port on the computer. If your device only has USB-C, use a known-good adapter. For phones: remove thick cases or wallet cases and tap the key slowly around the top/back area where NFC is usually located.
   This is your problem if: the key starts lighting up, vibrating, or being detected only when connected directly or tapped in a different position.
   Jump to: Fixes → USB/NFC connection problem

3. Unlock everything and complete the touch/PIN step
   Unlock the computer or phone, keep the browser tab in front, and when prompted, touch the metal contact/button on the key for 2-3 seconds. If the browser asks for a security key PIN, enter the PIN set on the key itself, not your account password.
   This is your problem if: nothing happens until you unlock the screen, focus the browser tab, touch the key, or enter the correct key PIN.
   Jump to: Fixes → Device screen, browser, or key is waiting for user presence/PIN

4. Check whether this exact key is registered on your account
   In your identity provider or account dashboard, go to the security settings. The path varies by provider, but it is usually one of these: Profile/Avatar → Security, Account Settings → Security, or Two-factor authentication / Passkeys / Security keys. Look for a list of registered keys by nickname or date added.
   This is your problem if: there are no security keys listed, or the listed key names/dates do not match the key you are holding.
   Jump to: Fixes → The key was never registered, or you are using a different key

5. Rule out device policy or OS restrictions
   If this is a work-managed laptop or phone, retry the same sign-in on a personal device you trust. If it works there, the issue is likely policy on the managed device. On phones, also confirm NFC is enabled in the device settings.
   This is your problem if: the same key works on another device, especially a personal one, but not on the managed device.
   Jump to: Fixes → OS or company policy is blocking USB/NFC/WebAuthn

6. Test whether the key itself is faulty or locked
   Try the same key on another supported device and another website that already accepts your security key. If every site and device fails, the key may be damaged or locked after too many wrong PIN attempts.
   This is your problem if: the key fails everywhere, or the prompt explicitly says the PIN is blocked or the authenticator is not usable.
   Jump to: Fixes → The key itself is faulty, low power, or locked

Fixes

Browser or sign-in flow is not using the security key correctly

1. Open the sign-in page in an updated browser: Chrome, Edge, Firefox, or Safari.
2. If a passkey or password manager sheet appears, click the alternate option such as:
   • Use another method
   • Security key
   • Use a different device
   • Try another way
3. If you have browser extensions that intercept sign-in prompts, open a private/incognito window and retry.
4. If the page was opened inside another app (for example, an embedded browser in chat or email), copy the URL and open it in the full browser.

Verify it worked: the browser shows a native prompt asking you to insert/tap/touch the security key, and sign-in completes after you do so.

USB/NFC connection problem (hub, adapter, port, case, cable)

1. Move the key to a built-in USB port on the computer.
2. If you must use an adapter, swap to another adapter you know works for data, not just charging.
3. Avoid these during testing:
   • USB hubs
   • monitor USB ports
   • keyboard passthrough ports
   • long extension cables
4. For phones using NFC:
   • Turn on Settings → NFC or Settings → Connected devices → NFC if present.
   • Remove thick or metal phone cases.
   • Tap the key against the top/back of the phone for 2-3 seconds and move slowly if needed.

Verify it worked: the key is detected only after direct connection or proper NFC placement, and the sign-in prompt advances.

Device screen, browser, or key is waiting for user presence/PIN

1. Unlock the device fully.
2. Keep the sign-in tab active in the foreground.
3. When prompted, touch the key's contact/button.
4. If asked for a PIN, enter the security key PIN. If you do not know it, stop guessing after one or two tries.

⚠️ Too many wrong security key PIN attempts can lock the key and may require a reset. A reset can remove credentials stored on the key and break sign-in for accounts that depend on it.

1. If you are unsure whether the prompt is asking for your account password or the key PIN, cancel and restart the sign-in flow from the website, then read the prompt text carefully.

Verify it worked: after touch or correct PIN entry, the site proceeds to the next login step or signs you in.

The key was never registered, or you are using a different key than the one on the account

1. Sign in using a backup method if available:
   • backup codes
   • authenticator app
   • another registered security key
   • admin-assisted recovery through your organization
2. In your provider's dashboard, open the security page, usually Profile/Avatar → Security or Account Settings → Two-factor authentication.
3. Check the list of registered security keys.
4. If your current key is missing, add it using the provider's Add security key or Add passkey/security key option.
5. Give the key a clear name such as Blue USB-C key - office.

Verify it worked: the key appears in the registered list and works on the next sign-in attempt.

OS or company policy is blocking USB/NFC/WebAuthn

1. Retry on a different trusted device.
2. If the key works there, contact your IT/admin team and tell them: Security key/WebAuthn works on another device but not on this managed device. Please check USB/NFC/security key policy restrictions.
3. On phones, enable NFC in settings before retrying.
4. If your browser was installed long ago, update it from the browser menu (Help → About) and retry.

Verify it worked: after policy adjustment, browser update, or enabling NFC, the managed device detects the key and completes sign-in.

The key itself is faulty, low power, or locked after too many PIN attempts

1. Test the key on another supported device and account.
2. If the key has a battery for NFC/Bluetooth features, charge it if your model supports charging.
3. If you see a blocked-PIN message, use a backup sign-in method first.
4. Replace the key if it fails everywhere.
5. After regaining account access, register a new primary key and a backup key.

⚠️ Do not reset a security key unless you understand the impact. Resetting can erase credentials stored on the key and may remove access to accounts where it is the only registered factor.

Verify it worked: a replacement or recovered key can be added in the account security page and succeeds on a fresh sign-in.

Prevention

• Register at least two security keys per important account. In your account security page, add a primary and backup key, and label them clearly, for example USB-C desk key and NFC backup key.
• Store backup recovery codes offline. In the provider's security page, use the Generate or Download recovery codes option and save them in your password manager's secure notes or a printed sealed copy.
• Keep one fallback method enabled during rollout. If your policy allows it, keep an authenticator app enrolled until you have confirmed both keys work on your usual devices.
• Test on every device type you actually use. After registering a key, sign in once on your laptop browser and once on your phone browser so you catch USB-C, NFC, and browser issues before an urgent login.
• Avoid fragile connection paths. Prefer direct USB ports over hubs for first-time registration and important logins. If your laptop requires USB-C adapters, keep one known-good data adapter with the key.
• Document key ownership and registration dates. In your internal access tracker or password manager note, record which accounts each key is registered to, the nickname used, and the date added. That makes it much easier to tell whether you are holding the right key during an incident.

This article was written by an AI system and published pending human review. Verify anything you intend to act on.