Using WebAuthn to Secure Your Digital Life

Since ancient times, we have used passwords to grant access to privileged information. Guards allow access to buildings if correctly presented with a password. Soldiers exchange passwords and counter password to correctly identify each other. Even 8-year old secret societies allow entry to magical tree forts after declaring the super-duper secret passphrase. And when computers were first invented, how did we decide how to secure them? Passwords! Because, well, that’s all we had.

But if there is anything that we have learned since Robert Morris first started storing login passwords in a hashed form in the 1970s, it is that passwords are messy. They are hard to remember, easily guessed, and annoying if leaked.

We Are Getting Better

However, in recent years, we have become more clever in securing digital accounts past just passwords. The two most significant things you can do to make yourself more secure online:

1. Use a Password Manager to create and store unique passwords for each of your accounts.
2. Turn on Multi-factor Authentication for all your highly sensitive accounts (like your bank and email).

But passwords, those things you and I have to remember if we ever want to use anything on the internet a second time, are still at the heart of the login process. Your password is the single key that proves you are, in fact, you. If a hacker manages to steal it, they can fully impersonate you unless you are one of the 28% of users using two-factor authentication.

Passwords are messy.

How Can Webauthn Help

As of January 2021, all major browsers like Chrome, Edge, Firefox, and Safari now support the Web Authentication API meaning we now have the ability to use Public Key Cryptography to register and authenticate users instead of passwords! You might be saying to yourself, “Public Key - what??” Don’t worry. You don’t need to understand the underlying technology to use WebAuthn. If that is you, you can skip to the next section. Otherwise, let’s dive into the details.

Public key cryptography is a relatively old concept but relatively new to user passwords. Ironically, it was invented in the 1970s, around the same time our friend Robert Morris was starting to store hashed login passwords. Public key cryptography uses the concept of a key pair; a private key that is stored securely with the user and a public key that can be shared with the server. These “keys” are long, random numbers that have a mathematical relationship with each other. This technique essentially became the cornerstone that secures most of the modern internet. However, its brilliance of shared secrets was never really applied to managing user passwords... until now!

The Web Authentication API (also known as WebAuthn) is a specification written by the World Wide Web Consortium (W3C) and The Fast IDentity Online Alliance, known as FIDO, with the participation of Google, Mozilla, Microsoft, Yubico, and others. WebAuthn allows users to authenticate with public-key cryptography using one of two options:

• Roaming authenticators — These are removable and cross-platform devices, like a Yubikey that can be used on multiple devices. To authenticate with a roaming authenticator, you simply connect it to the device (through USB, NFC, or Bluetooth), provide proof of presence (e.g., touching it), and optionally an additional authentication factor like a PIN or fingerprint recognition.
• Platform authenticators — This option includes the MacBook’s TouchBar, Windows Hello, iOS TouchFaceId, and Android’s fingerprintface recognition. Integrated into the device being used, these only work on that device.

In the context of this article, we are focusing on Roaming Authenticators, but just know that WebAuthn enables both, opening up a lot of possibilities for secure user authentication in the future.

Want to learn more about WebAuthn?Visit → webauthn.me

How to Set up and Use a Security Key

What you will need:

• A laptop or desktop
• A modern browser installed, either Chrome, Firefox, Edge, or Safari.
• A hardware security key, the two best options are Yubikey or Google Titan. Mine looks like this:

Note: Before getting started, be aware of what you are about to do. You are about to register a hardware security key as a second form of authentication for your various accounts. If you do not have this key physically present with you when logging in, you will not be allowed to continue. It would be wise to enable Two Factor Authentication initially via a Temporary One Time Passcode mobile app like Authy or using text messages sent to your phone number. This ensures that if you ever lose your security key, you can still use a second form to sign in. If you have not done this yet, you should do this now.

And if you haven’t downloaded and saved your recovery codes in a secure location like a password manager, you should do that as well. Recovery codes can be used to access your account in the event you lose access to your device and cannot receive two-factor authentication codes.

How to set up a security key with Google

1. Log in to your Google account from your browser.

2. Choose Security from the options on the left-hand side.

3. Under Signing into Google, select 2-Step Verification.

4. Under the Add more second steps to verify it’s you section, choose Add Security Key.

5. Choose USB or Bluetooth option.

6. Follow the instructions to register your security key.

7. Once completed, you should see your named security key as the default option (since it is the most secure) to finish signing in after you enter your password.

How to set up a security key with Twitter

1. Log in to your Twitter account from your browser.

2. Click on More and choose Settings and Privacy.

3. Select Security and account access and then Manage your account’s security.
4. Select Two-factor authentication.

5. Click the Security key check box.

6. Follow the instructions to register and verify your security key by touching it.

7. Your key should now be registered with Twitter.

How to set up a security key with Github

1. Log in to your GitHub account from your browser.

2. Click on your profile image in the top right, and choose Settings.

3. Select Account Security, then Add.

4. Under Security keys section, register your new security key.

5. Enter a name for this security key.
6. Follow your browser’s steps to register your security key.
7. Insert your security key into your computer and touch it.
8. Your key should now be registered with GitHub!

It is that easy! You have now made a giant leap in securing your digital life all thanks to WebAuthn.

On a day-to-day basis, you may not be required to use your hardware key all that often. Services often consider different risk factors to determine whether to require it. Some sites may ask you to enter it when you’re managing what kind of authentication you’re using, while others may ask you to use your key only when you’re logging in from a new computer.

How to Set up Security Keys for Your Company

If you manage a company’s customer identity access management, then giving users more secure ways to protect their accounts can drastically reduce your risk. One of the easiest (and most secure) ways for you to implement WebAuthn with Security Keys for your website is allowing Auth0 to manage it for you.

A Beta release of Auth0 with WebAuthn support for Security Keys is available starting today. You can enable the second factor in the WebAuthn with Security Keys MFA configuration section of the Auth0 admin dashboard:

After it is enabled, users will go through the enrollment flow below. At some point, their browser will show a native dialog to ask users to engage the security key. In the example below, we show the Android dialog:

The next time they login, the flow will look like this:

Passwordless Future

Now let me give a fair warning, we are still on the cutting edge of this technology. Even though browsers now support it, most companies have been slow to adopt WebAuthn, and where there is support, it is only used as a second form of authentication. In other words, we are still a few years from seeing true passwordless user authentication, but it is a start - a very promising start.

What we need is more people insisting that companies start implementing WebAuthn as a primary form of authentication. And the best way to do that is by demonstrating there is public demand for such feature requests by utilizing what is currently offered today.

WebAuthn is an exciting technology, and Auth0 is committed to providing the best possible implementation, maximizing security without sacrificing user experience. Please try our Beta today and let us know what you think on our Feedback page or in the Auth0 Community .