Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Please read this blog if you want to find out why you must reconfigure the Yubikey Hardware token.

titleWhy do I need to configure the Hardware token (Security Key) again?

Chrome is deprecating the support of its legacy U2F APIs (which are used by the Hardware tokens) in February 2022. So all the apps need to migrate to WebAuthn APIs.

In the recent chrome version, Chrome has disabled the U2F support by default. So if you are using Chrome then you must be getting a warning message on the Chrome browser as below whenever you try to login to your Jira or Confluence account and use Yubikey Hardware Token(U2F).

After February 2022, you will not be able to use U2F APIs. To avoid that, please configure your Hardware token again. This will be a one time process.

Please check the steps given in the section below to find out how you can reconfigure the Hardware token/Security Key.

titleHow to reconfigure the Hardware token (Security Key)?

The reconfiguration is a very short and simple process. You need to follow 3 steps.

Step 1: Click on the Reset and Logout button. You will get logged out from your Atlassian application (Jira/Confluence)

Step 2: Log in to your Atlassian app again.

Step 3: After login, configure the Two-factor authentication again. (Using the same Security Key.)

Complete these 3 steps and you are good to go.

titleIs it required to change the USB security keys?


The USB security keys used for U2F registration are compatible with WebAuthn APIs as well. So you can continue using the same USB keys.