# Onlykey stopped working with Vanguard.com on September 20th, 2022

**URL:** <https://onlykey.discourse.group/t/onlykey-stopped-working-with-vanguard-com-on-september-20th-2022/858>\
**Category:** Two Factor Authentication\
**Created:** [October 1, 2022, 11:23pm UTC](https://onlykey.discourse.group/t/onlykey-stopped-working-with-vanguard-com-on-september-20th-2022/858 "2022-10-01T23:23:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pat](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@Pat](https://onlykey.discourse.group/u/Pat)\
**Post date:** [October 1, 2022, 11:23pm UTC](https://onlykey.discourse.group/t/onlykey-stopped-working-with-vanguard-com-on-september-20th-2022/858/1 "2022-10-01T23:23:20Z")

</div>

I’ve been successfully using my Onlykey for 2 factor with my [Vanguard.com](http://Vanguard.com) account via Firefox until they upgraded on September 20, 2022. The site tells me I need to reregister my key. I follow their steps exactly but on the last step, it says touch your Onlykey to verify it’s you. I do that and then it just fails back to the first step saying you must reregister your Onlykey. I’ve seen mentioned in a few places that [Vanguard.com](http://Vanguard.com) only accepts Yubikey but I’ve been using my Onlykey successfully until September 20, 2022. Anybody here experienced this?

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [October 6, 2022, 1:38pm UTC](https://onlykey.discourse.group/t/onlykey-stopped-working-with-vanguard-com-on-september-20th-2022/858/2 "2022-10-06T13:38:01Z")

</div>

The only thing I can think of here is there may have been a transition from FIDO U2F (the old standard) to FIDO2 (the new standard). Are you able to re-register your OnlyKey at [Vanguard.com](http://Vanguard.com) in another browser?

---

<div class="post-metadata">

**Author:** ![SimpleHominid](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@SimpleHominid](https://onlykey.discourse.group/u/SimpleHominid)\
**Post date:** [October 29, 2022, 9:39am UTC](https://onlykey.discourse.group/t/onlykey-stopped-working-with-vanguard-com-on-september-20th-2022/858/4 "2022-10-29T09:39:24Z")

</div>

I am seeing the same thing; using both Firefox (106.02) and Edge (106.0.1370.52).

They did a transition to FIDO2 on Sept. 20 based on the e-mail that I received and ignored. It still has my original registration as a U2F (based on the URL strings: [Log on to vanguard.com - personal investors](http://personal.vanguard.com/us/U2FKeyEnrollment) ); which it doesn’t allow me to delete.

I tested the OnlyKey FIDO2 against the Yubico Demo page ([Yubico demo website](https://demo.yubico.com/webauthn-technical)) and no apparent errors there. Device was identified as unknown.

I’m probably missing something simple here.

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [October 31, 2022, 3:15pm UTC](https://onlykey.discourse.group/t/onlykey-stopped-working-with-vanguard-com-on-september-20th-2022/858/5 "2022-10-31T15:15:44Z")

</div>

Unfortunately, Vanguard only supports Yubikey currently. It was probably working because with the older browser this didn’t support FIDO2 so the site failed back to U2F. If you could contact Vanguard and ask their support if they support security keys other than Yubikey now or plan to in the future we could get some clarity here.

---

<div class="post-metadata">

**Author:** ![SimpleHominid](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@SimpleHominid](https://onlykey.discourse.group/u/SimpleHominid)\
**Post date:** [November 1, 2022, 12:46am UTC](https://onlykey.discourse.group/t/onlykey-stopped-working-with-vanguard-com-on-september-20th-2022/858/6 "2022-11-01T00:46:20Z")

</div>

Thanks for the reply. I’ll ask them about it and post back here.
